A Process is an execution flow of services and logic defined by the user. The flow is directed from Start to Terminate by connecting directional lines to services along with other process flow elements, such as a binary decision, which may cause the logic to branch off into a different flow based on some criteria. The end result looks like a flowchart and it visually represents the logic to be used in various scenarios.
There are different types of processes as well: (Note: The main difference of the types of processes are what triggers the process to occur and how they are used)
- Can be called from another process by its Process Id
- Can be scheduled as a window's task to run on a schedule.
- Ex: Every day, run a process that sends the admin an email with details on who has completed a registration request and requires action for a user to be created for the site.
- Process is triggered when a button in a webpart is clicked
- There are also processes that can be attached to other input fields such as a Drop Down List or Textbox as long as you turn Auto Post Back on for that field. (Allows the page to post and triggers the process).
- Ex: A save button on a form would collect the user entered information and save it into the database.
- Process which defines data for a datasource. This can be one node of the process mapped to one field or it can be many nodes mapped to a list section of fields.
- Ex: This is the logic that could determine what text should show to the user in a drop down list. What values does each option in the drop down list have associated to it (different from the descriptive text the user sees)?
- On-Load Process (Web part and section)
- Triggered each time the Web part or section is loaded.
- These types of processes are only recommended for use in a list section. All other uses (regular sections, web parts) are deprecated. This is because often the logic you need to accomplish in a regular section or Web Part onload, could be done in a process Data Source to consolidate queries.
- If this is used for a list section (which can display many times, once for each record to display in the list), the onload runs once for each record in the list section.
- Ex: If there were a grid (list section) which listed all the past orders the user has placed, an onload process could look at each order (list section record) and calculate the order total based on the items within the order. The process would run once for each order(record in the list).
- Use list section onloads cautiously. Queries should pose no issue, but if there are many unions, a query could become slow. JDE Business Functions should also never be placed in onloads as the run time for the web part could be drastically increased. If a list section on-load takes as long as 1 second, the list section will take 10 seconds to load for 10 records.
- On-Pre-Render Process (Web Part and section)
- Same as On-Load but executed after On-Load
- The use of these processes is not recommended. Although some may still appear in older webparts, this feature is deprecated.