Action Vs Page

[AndrewMullin1]

Within a process is it better practice to use an Action or a Page to execute different pages? When should one be used over the other?

What specifically is the technical differences between the two?

[Ben.Lyons1]

Hi Andrew,

An action refers to a 'page' within an object and would correspond to an action for the application in use. These should be kept relatively short, to maximise re-usability.

A page in the context of a process is likely to be a collection of actions, decisions, calculations, etc. This will be a sub-section of the overall process and can be used once or multiple times within the process. For example it might be the actions to launch and log into the application or the sequence of actions to create a new record.

A key difference is that an action should not contain any business logic, as this would make it less re-usable. Where a process will contain the decisions that change how the work item is handled. Such as a different product needing to be routed down different process paths.

There's a useful course on Blue Prism University, Development Best Practice. If the link doesn't work, simply search Development Best Practice in the courses.

Regards

Ben

[EVIPUTI]

A process is made up of one or more pages. Likewise an object but in the case of the object, the pages are called Action's. Pages are called from process flow for ease of maintainability and is followed as part of best practice. Complex objects are further bifurcated by calling page logic. By default, when you create a process, it has only one page called the Main page, which is the starting point of your process. You can create multiple pages and have them been called from the main page. The idea of creating is to abstract some bits of related logic/functionality. A key difference is that an action should not contain any business logic, as this would make it less re-usable. You should have all your logic in the Process studio to create your actions flow and there yes, you use multiple actions from different objects in the same page.