I have created changes to a table/app to allow for record templates and remove any clear on copy for some fields. I am able to test manual record templates in my LC and work as expected. I created a recurring record template and there is an option in Edit Recurrence Rules to RUN NOW. When I selected that, it ran but in base lifecycle, which error’d due to a validation it would not hit if it ran in my LC, which I was in. Anyway around this? If not, any enhancements planned for this?
Absent someone else responding, that seems like a possible bug to me.
If you are a Nextworld customer or partner, work with your system administrator to submit a ticket with customer support, who will file a bug on your behalf. Include a link to this post in the ticket. If you’re not a Nextworld customer, keep an eye on release notes. We’re always making improvements.
I have posted a bug with a link to this post. TY
Workaround Steps to Unblock:
- Open the Job Scheduler application and search for the job.*
- Inactivate the job, then deselect Run in Default Lifecycle.
- Update the Run in Lifecycle to your lifecycle.
- Reactivate the job.
*Note: If you have only one recurring template job set up, it’s easy to locate since:
- The Category in Job Scheduler will be Template
- The Owning Record Application will be the application where you enabled templates
If you have multiple recurring templates, you can use Developer Tools to find the job nwID and search for it in Job Scheduler.
1 Like