Skip to main content

Updating existing actions in bulk

One of the change requests currently supported in 1:1 Operations Manager is the Action update change request. Initiating this request triggers a process for updating the properties of single or multiple actions. Within the Action update change request, the Bulk Edit option is available, streamlining the creation of change requests aimed at updating several actions with one specific modification.

Updating existing actions in bulk

In 1:1 Operations Manager, there are three types of change requests that are currently supported:

  • Create Action
  • Create Action update
  • Create Other

In addition to single action updates, the Action update change request type enables you to perform bulk updates on always-on actions. A bulk edit feature is a valuable option when you need to implement a specific change across multiple actions. For instance, if a business requirement entails modifying the availability of 100 actions, instead of creating change requests and modifying settings separately for each action, you can make a unified modification. The bulk update simplifies the process of creating change requests for multiple actions.

Consider the following scenario: U + Bank, a retail bank, wants to limit the availability of two actions: the Rewards Card and Rewards Plus card, and make them available only for the next two weeks.

To meet the business requirement, you need to design a bulk edit change request. As a Business user, create the Action update change request and select the credit card actions that require editing.

Action update

 

In the Detail Updates for Selected Actions stage, the Bulk edit option becomes accessible when you choose two or more actions from the list. In this case, select the Rewards Card and Rewards Plus Card, and proceed with the bulk update. The bulk edit option supports several predefined tasks. In this case, modify the action availability.

Bulk availability update

 

Within the Edit 2 actions window, you can set the actions as available at all times (always visible to customers), unavailable (never active), or within a defined time period (visible temporarily). Adjust the availability timing according to the requirement, and submit the change request.

Availability update

 

After you successfully create the change request as a Business User, log in as a Team Lead to prioritize the change request.

The next step is to complete the action build task. Log in as an NBA Specialist and check if you can see two tasks, one for each action. Despite having created a single bulk edit change request for multiple actions, as an NBA Specialist, you should complete tasks individually.

Assign the first task to yourself and finalize the task by reviewing the availability setting. Given that the Business User has updated availability during the planning stage, the build stage only requires verification and confirmation of the changes. Upon completing the build stage, review and submit the task. Repeat the same process for the second task and then submit the changes.

Following the submission of updates by the NBA Specialist, log in again as a Team Lead to approve the updates and promote them for deployment.

The final step in the process is to deploy the changes to production using Operations Manager.


This Topic is available in the following Modules:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice