- This workflow is missing the key field Employee self service skills.Person when user is doing Conditional decision and select in Edit condition - Where Workflow.Workflow originator - is - field - (possible fields selection here is Employee self service skills.Created by, Employee self service skills.Modified by.
- Missing key field Employee self service skills.Person is stopping the configurable possibilities in the workflow
- Data source Employee self service skills is already attached to the standard skills related workflow
- Workflow will have from this Data source related 2 fields already (Created by and Modified by), but the key field Employee self service skills.Person is missing from the list
- When the key field would be included to the workflow, it gives a lot of possibilities to create different configurations for workflow
- Field addition will not mixed up any processes or existing workflow configuration for other customers
Comments
I was able to set up a conditional decision with following condition as a workaround for this issue:
Where: Workflow.Workflow originator is field User to person relationship.User ID
As expected, this decision takes one route in the workflow if the submitter and the person whose skills are modified are the same user (condition is true), and another route if someone has submitted a change for someone else (condition is false).
Category: Employee and Manager Self-Service
There is already one idea for this purpose placed: https://experience.dynamics.com/ideas/idea/?ideaid=2c0d65c7-8fbf-e911-b083-0003ff68a4c7
Workflow condition possibility should be related to all ESS employee information like skills, certificate etc. HR person or manager can update these information and would require different workflow path in that case.
Category: Employee and Manager Self-Service
The same need is for certificates workflow.
- employee itself will do insert or update
- manager will do insert or update and approves certificates for his team members
Category: Employee and Manager Self-Service
Standard skills related workflow would be much more configurable to the different business cases, if workflow condition could use Employee self service skills.person field.
With this information workflow could make condition rules comparing workflow originator to the Employee self service skills.person and workflow could guided to the different processes, when
- employee itself will do insert or update
- manager or HR person will do insert or update
This would bring much more possibilities to the standard workflow without any new feature design for the skills approval.
Category: Employee and Manager Self-Service