mahesh reddy · Follow
5 min read · Mar 27, 2021
--
As a PEGA creator, our minds immediately think about writing an operation as a first possibility once we start dreaming about a use case. Since the operation has several choices and seems to be an algorithm or software that we are familiar with. But why does PEGA recommend that we restrict the number of activities we use? What happens if we establish an action rule? This is a concern that most of us have in our heads. Let’s go back to the beginning and figure out what’s going on.
Obj action rule
The Rule-Obj-Action rule form is an instance of an activity. The Process Commander system’s fundamental sequential processing unit is an operation.
While describing, an operation is made up of a series of steps, each of which may include a procedure or instruction. The framework transforms the details in an operation form into server-side Java source code when you save it. This Java code is compiled and executed at runtime to perform encoding, analysis, and decision-making.
If you are interested to Learn pega you Can enroll for free live demo Pega Online Training
Differentiate one operation from another
Fields for each operation parameter exist whether it includes Call, Branch, Collect, Flow-New, Queue, or Rule followed by a space and an activity term. You should specify that this activity’s parameter page will become the parameter page for the goal activity (“parameters passed by reference”).
Run two PEGA activities at the same time
To initiate asynchronous execution of a second operation, use the Queue command. In cases where there is no need to wait for the second operation to finish, or where parallel processing is possible. Then you can benefit, this is an alternative to the Call instruction.
- BRANCHING — Going from one activity to another.
Use the Branch instruction to allow the current operation to look for and the branch to another specified activity without returning. When the branched operation completes, the current activity’s processing completes as well; no actions after the Branch stage are performed. Another operation is referred to as a CALL.
- COLLECT — Begin a collection rule’s execution.
- FLOW-NEW — Initiate a new flow.
- JAVA — Using Java in a phase of an operation
- QUEUE — Execute asynchronously some operation.
- Law — To enforce a custom rule form, use the Rule instruction (Rule instruction is deprecated.
Note:
The law instruction is no longer sponsored. Call the assess Law operation instead. To find another operation called evaluateRule that implements a custom rule form, use the Rule instruction. Power is transferred to the operation as this instruction is executed.
PEGA activities
Activity guidelines are similar to standard programming systems in that they are made up of a series of steps that must be completed in a certain order. A process is made up of a series of steps, each of which includes a process. An operation will, for example, retrieve a work item from the database, compute new values for some of the work item’s properties. Then save the modified work item back into the database. A user interface can be supported by an operation law that performs computations, creates, updates, or deletes objects.
PEGA Characteristics
The majority of operations have no more than 20 stages. Based on a conditional test, activities will run in sequence or skip ahead to a later-numbered stage, marked by a marker.
- You can contain a set of procedural, atomic steps that are performed top-down by default.
- Then correspond to a particular instruction (known as a method) in each stage
- Thus, can perform calculations, retrieve, refresh, and save data, and call other operations.
Getting Problems with Practices in PEGA
1. Susceptible to security
Since java steps or javascript may be written within operations, they are vulnerable to several security attacks. To protect our framework from multiple security threats such as Injection and Cross-site scripting, Java code must be properly written.
2. Deadlocks and endless loops
It will also go into an endless loop due to poor coding or unexpected feedback, resulting in deadlocks. Both PEGA rule styles cover these situations out of the box, but operation logic is custom written, so it’s up to the creator to make sure they don’t end up with spaghetti code.
3. Issues of Complexity and Maintainability
Activities, unlike other rule forms, will add complexities to the framework. It’s very difficult to assess and debug problems with operation rules. Although activity rules are necessary to learn and implement where needed, they are not the most common or primary rule form in applications.
4. There are no declarative activities.
The ability to invoke rules decoratively, such as Data tab, Declare Expression, Declare Index, Declare On Shift, and so on, is a powerful function of PEGA. We must specify informal fashion somewhere in our flow because the actions do not have the power to invoke themselves declaratively.
5. Your experience is limited by your activities.
Because of the scale and strength of the tasks, developers do not have any other alternative than to use operation guidelines to meet their goals. Developing, debugging, and maintaining it takes time.
So, from now on, aim to use fewer behaviors and instead focus on the other rule types offered by PEGA. The last choice that we should consider is operation. PEGA provides a new and upgraded range of functionality for each update to remove operation usage; we’ll go through the new features in the next post. Finally, a strong PEGA experience would not allow you to come up with new practices.
Types of Activities in PEGA
The Work-based class, or a class derived from the Work-based class, defines the majority of activities in a flow. They must satisfy other constraints to have this form registered in the Task Type area of the Security tab to become a Notify, Integrator, Utility, Routing, or Assignment activity.
Show of verbalization
Choose Behavior > To see a step-by-step verbalization or English text summary of this operation, preview or enter the corresponding keyboard shortcut CTRL+ALT+P. The framework generates an HTML subject for each step of the operation, along with links to other guidelines that the step references.
Lost operations and uncaught exceptions are processed and presented.
When a top-level task completes but no HTML output is generated, a “No content” type with a green checkmark and the message “The process completed successfully but returned no content” appears by default.
When an operation fails or an uncaught exception occurs, a “Please notify your system administrator” window with a red X mark appears by default: Your program will bypass and localize the standard harnesses that display these two windows, as well as the standard operations that call the harnesses.
An operation within an expression is referred to as.
The Pega-RULES Utility library’s basic feature call activity() calls an activity but only returns void, not a value output. You may use an expression to do an operation, but only for its side effects. The main tab, the operation page, and the parameter page should all be defined. Consider the following scenario:
Utilities.callActivity(pyWorkPage, MyActivity, tools.getParameterPage()); @Pega-RULES:Utilities.callActivity(pyWorkPage, MyActivity, tools.getParameterPage());
Note:
If you want to learn how to call activity() in a custom mobile app indirectly, keep reading.
Conclusion
Many of them, like me, may have ended up repeating 10–15 strategies. This is in an operation law to get tasks done. It’s mostly due to a lack of knowledge of how to employ such approaches properly. You can know more about PEGA activities through PEGA online training.
