Action in Summary View

Record actions can only be generated, or built manually. As of now, Appian does not generate any record action interfaces without the related process model.

Can you help me to better understand your specific use case?

This is my summary view and i want to add an option that says "Apply" so that it will take me to another interface where i can fill in the details. How can i do that ?

Create a new process with a process start form, add the required process logic, and add it as a related action.

Can't i use the add view manually option to add a new required action, is that possible ?

You can use the approach suggested by Stefan and start a process with a startProcessLink instead of using an action.

Yes, add this new process manually.

But, what is a "required action"? If this is more of a task a user has to complete, I strongly suggest to implement this in a process model which is initiated when a new item is created.

Keep in mind, that an Appian process model can/should directly coordinate the tasks in a process. People used email, Excel, phone to do all of this process operations manually. This is what we can automate with Appian. A record with a bunch of related actions will not make it.

Yes, add this new process manually.

But, what is a "required action"? If this is more of a task a user has to complete, I strongly suggest to implement this in a process model which is initiated when a new item is created.

Keep in mind, that an Appian process model can/should directly coordinate the tasks in a process. People used email, Excel, phone to do all of this process operations manually. This is what we can automate with Appian. A record with a bunch of related actions will not make it.

Well to be brief, 

I have created a job listing portal where you can view the job openings and when you click on the job id you will be taken to the summary view where the update, delete and apply for job actions are available and when you click "apply for job" action you will be given some fields you have fill like in the normal form you fill in any other job portals when applying for a job.

Understood. This kind of activities is exactly what record actions are made for.

so i need to create an interface first and then call it in the reacord action so it can be used as a link ?

Views and Actions are two different parts of a record, Summary is a view and Delete / Update record in an action.

skzahed_09 said:

Can't i use the add view manually option to add a new required action, is that possible ?

To apply for job you will need to have an action. Actions are created using process models. Process model can contains user interface and smart services for data management. 
For your use case you should create a process model having expected interface as well as smart services like write records etc as needed. Then add that process model as a related action in your record. Then in the Views section of record mark the checkbox for that action to be visible in summary view. 

I suggest to have a detailed look at your automatically generated record actions. You will have to build the same objects, just tailored to your use case.