Custom CC Workflow Email Notification

[esinanya]

Hi,

We configured a custom workflow email notification to be sent on new hire, it worked well in QAS yet in production (no difference in terms configuration, locale etc) we still get the standard one. We have checked all the KBAs, raised a ticket on launchpad too, but couldnt find any solution.

We saw a similar post in the community, according to that post changing the order of the business rules would work, yet it did not work. Anyone has ever experienced this before? Thanks,

[Angie_Pullano]

Hi Sinan,

I have previously encountered an issue where when the custom email included previous/new value tokens, that if there was more than one action on the same day, the system would send the default email instead of the custom email. That resulted in users sometimes getting the custom email template and sometimes the standard email template for the same workflow.

I would suggest taking a look at the tokens being used in the custom template and if the employee has more than one action on the effective date.

Best regards,

Angie

[Praveen_Kumar]

I have the same issue. The standard email template is used instead of custom for cc role. Checked all the options.

Any solution?

[esinanya]

I would like to bring to your attention that we have discovered missing RBP permissions for the group responsible for triggering this email.. Please refer to the attached screenshot for details.

Usually all document generation related objects are pre-delivered as "Non-Secured". To access these objects, the permission role "Metadata Framework -> Access to non-secured objects" must be granted.

However, in our situation, the objects have been marked as "Secured" in the "Configure Object Definition" screen. Therefore, miscellaneous permissions needed to be granted in order to access them.

Thanks, regards,

Sinan

[esinanya]

Dear Jasper,

Many thanks for your help.

None of the dynamic group members or roles that we included in the workflow receive the custom email that we created.I confirm that we have checked all the things that you have indicated and the configuration is exactly same as QAS.

However, there might be some differences in provisioning. What is the job that could be missing in production?

Thanks a lot.

[nlgro023]

I've had issues in the past with getting it through, but that was rather due to a job in provisioning not being turned on. For anyone to assess what could be the issue we'd need a lot more info than this as it could be:
- That the person that should receive the info is not in the role/group that should get it
- That the person (in a group) doesn't have a fitting email
- That the content reaches the spam
etc.