Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Editing event codes

Updated on August 31, 2021

Event codes use versioning to manage history and changes to the configurations. Editing an existing event code is performed via the action Create new version that is available by selecting the button on the event code list or on the Actions menu on the event code information screen.

In addition, for an event code that has a version configured for a future date, the Edit version action is available. The Edit version eliminates the need to create a new version for a future configuration that needs modification.

If the Edit version or Create new version actions are not available, in the list or Action menu, an existing update for this event code is pending approval.

These actions open the Event code information screen for modifications. The fields for modifications are the same as those used in creating a new event code. Once the modifications have been completed, the changes, along with a comment for the approver, can be submitted for approval. A new version will be created once these changes are approved. You can discard the changes or save for later if appropriate.

If the version start date or end date conflicts with an existing version of this event code an appropriate warning will be displayed. The end date of the previous version will be populated once the new version is approved. This date will be set to the start date of this new version minus one day. If the new version start is set to today, a warning stating that this date might be changed on approval will be displayed prior to submission.

Version date warnings:

WarningScenario
Version start date cannot be a past dateThe start of the version is in the past
Version start date is equal to the start date of an existing version, please reviseAn existing approved event code has been configured for the same start date
Version start date is earlier than the start date of an existing version and contains overlapping dates, please reviseThe configuration for this event code contains version dates that overlap an existing approved event code. The start of this event code is prior to the start of the approved event code
Version start date and end dates are before and after the version start and end dates of an existing version, please reviseThe configuration for this event code covers the version start and end dates of an existing approved version.
Version start date and end dates are within the version start and end dates of an existing version, please reviseAn existing approved version covers the configuration for the version start and end dates for this event code.
Version start date and end dates overlap multiple existing version start and end dates, please reviseThe configuration for this event code overlaps multiple other approved event codes

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us