Thanks Chris! QA are more immediately impactful in the EC world, but AI is still pretty cool. I did the image on the thumbnail with Dall E 3. After a few prompts it looked perfect.
Hi! Thanks for this video. Very helpful, however, I'm having an error after Manage Data>Create New>Employee Central Quick Action Template>Use Case=Change Location (or any value that I select)= error: No data availability or you do not have necessary permission. Please help! Thank you
Hey Brandon, nice video as always. What if e.g. position is leading usually for such data? Then you can't use those fields? e.g. for location? as a job2position sync is not possible? I was just wondering what you have for thoughts on this situation? thanks patrik
Location can synchronize back to the position using position reclassification. If you update the location on the employee, have a position follow-up activity on the event reason, and have a business rule under position management settings for job to position update, then the location change will update on the position. I did a video on why this is my favorite thing that EC does that SAP doesn't. ua-cam.com/video/gR5LCF9G4WM/v-deo.html
Great summary, Brandon! Thanks for that 🙂 One question regarding "other standard fields": I couldn't add any standard field not inn teh predeifined scope to your example. But say, I need to review and possibly change the cost centre, when I change a location, but I don't have a unique dependency, so can't automatically change the cost centre via business rule based on location. Could I di the following (without suggesting it is elegant or a good idea): I create a custom field, hidden from view in the normal profile, but otherwise same as the cost centre field. Whenever cost centre changes, I change that field accordingly with a biz rule in the background. I add this custom field to the quick action, so the user can change it there. If it's changed, I write it back to the real const centre fields with a rule. So, the outcome would be the same as adding the actual cost centre field to the quick action, if I understand everything correctly, albeit with a dirty design? One concern: if the cost centre is updated indirectly from a quick action, would it still be written back to the position, when position reclassification is active? Any other problems you see with that approach?
Sven- Yes absolutely you could do as you say. (I do something similar with Employee Group/Employee Class in core hybrid implementations) I believe that SAP is going to be adding more scenarios in the future so I would hold off for next release before going to the trouble.
Thank you for the update...
Brandon Amazing Stuff, I like you wonderful bit size videos and explanation.. Keep Learning and Sharing
Awesome video mate! 👏 Agree with you that this is one of the most exciting bits of the release... Who cares about AI! 😜
Thanks Chris! QA are more immediately impactful in the EC world, but AI is still pretty cool. I did the image on the thumbnail with Dall E 3. After a few prompts it looked perfect.
I would like to congratulate you on the video.
And also tell you that at 11:26 it ends but continues black background until 21:03 . Best regards.
Thanks so much Juan! I hadn't noticed all of the extra at the end. I have trimmed it now.
Hi! Thanks for this video. Very helpful, however, I'm having an error after Manage Data>Create New>Employee Central Quick Action Template>Use Case=Change Location (or any value that I select)= error: No data availability or you do not have necessary permission. Please help! Thank you
Hey Brandon, nice video as always. What if e.g. position is leading usually for such data? Then you can't use those fields? e.g. for location? as a job2position sync is not possible? I was just wondering what you have for thoughts on this situation? thanks patrik
Location can synchronize back to the position using position reclassification. If you update the location on the employee, have a position follow-up activity on the event reason, and have a business rule under position management settings for job to position update, then the location change will update on the position. I did a video on why this is my favorite thing that EC does that SAP doesn't. ua-cam.com/video/gR5LCF9G4WM/v-deo.html
Great summary, Brandon! Thanks for that 🙂
One question regarding "other standard fields":
I couldn't add any standard field not inn teh predeifined scope to your example. But say, I need to review and possibly change the cost centre, when I change a location, but I don't have a unique dependency, so can't automatically change the cost centre via business rule based on location. Could I di the following (without suggesting it is elegant or a good idea):
I create a custom field, hidden from view in the normal profile, but otherwise same as the cost centre field. Whenever cost centre changes, I change that field accordingly with a biz rule in the background. I add this custom field to the quick action, so the user can change it there. If it's changed, I write it back to the real const centre fields with a rule.
So, the outcome would be the same as adding the actual cost centre field to the quick action, if I understand everything correctly, albeit with a dirty design?
One concern: if the cost centre is updated indirectly from a quick action, would it still be written back to the position, when position reclassification is active?
Any other problems you see with that approach?
Sven- Yes absolutely you could do as you say. (I do something similar with Employee Group/Employee Class in core hybrid implementations) I believe that SAP is going to be adding more scenarios in the future so I would hold off for next release before going to the trouble.
Let me know what you think of the new Quick Actions!