Automate sales content for Human resources

How to create outlook signature

in this demo a day in the life of human resources professionals and an employee with open text content services you will see highlighted key document generation capabilities design and deploy forms how data can be ingested via capture key process and automation capabilities identity capabilities appropriate for key roles such as end users developer and subject matter experts integration with enterprise applications such as success factors and end user participation and tracking for repetitive processes we will be using opentext extended ecm extended ecm for success factors and extended ecm for microsoft 365 with teams integration as well as our core capture solution in this hr retirement process automation usa case scenario watches are hr professional initiates a document automated steps are kicked off for easy collaboration with team members and employee engagement as well as intake of important information all connected together enabling multiple stakeholders to facilitate this hr employment retirement process efficiently and effectively in this administrative dashboard tessa can see all the document templates she's responsible for and she's going to make a change to the exit checklist template right now microsoft word is the design tool tessa is using where she keeps maintaining the static content the dynamic content and also form fields that will show up in the pdf form output as active elements so now now she's going to add an additional dynamic field for the bonus pi expiration date which is coming from success factor so from the palette on on the right hand side she can choose the field that is part of the data integration and with just one click she's adding it and completing the work of template editing the change document is showing in the this list here is a draft starter so the next necessary step is to activate this document and make it available for production use so once once that is done the the workflow inside success factors has a task to actually create a document so we'll take a look at that task now from the point of view of an hr administrator so this is the checklist to be used it's first of all empty and it's getting populated with the data right right now and you see the data filled in dynamically and this document is being saved in the workspace we want to automate the next action and the document generation is actually triggering an upload document event and we are going to use that upload document event to automate the notification in in microsoft teams so there is an action and we have a pre-configured library of operations integrating in all different systems here and tesla has chosen the up notification and teams action here for this process we are now switching over to udo the about to retire employee and udu is receiving a chat message in microsoft teams and this chat message is actually driven by the automation that we've just seen here so the notification about completing the the checklist and sending it back is coming in an automated way so he can open the document look at it it's a pdf form so he could fill it out online and and return it in a digital way but he could as well print it out and return it in paper this is the scanned document that tessa has received from udo we'll now demonstrate how she's going to add an additional field to be recognized so first she's starting in the in the extraction defining that field which is the termination date and and the second step this field is all tessa is also adding that field to the to the export to extended ecm so this termination date field is showing here as well and this is the expression for handing it over to extended ecm in the in the right format so once the definition of that recognition project has been saved is now published to the production core capture server and there it will be then in place after deploying now let's take a look at scanning the document and training the recognition engine so it starts with an unclassified document and based on some basic information you can see then that the recognition engine core capture is already identifying it as an exit checklist document with all three pages belonging to the same document now we'll look at the recognition of the metadata fields and that will start empty as the system has not been trained but with a simple point and click tessa is able to tell the system where to look for for those form fields like the termination date and with that the the training has been completed the document is now handed over to extended ecm based on the metadata information like the employing id is now put into the employee file or and also classified as an exit checklist document so let's do that again in order to unders see how the capture engine is actually recognizing the fields based on the training information that we applied in the first pass so as you can see now in the review step the fields have been extracted and you can see them highlighted to continue the automation we have again the upload document event which is triggered by co-capture which will drive another action plan and this action plan is yeah separated from the from the first one by a different rule expression so here we only are listening to events to triggered by documents coming into the off-boarding folder and the action is to drive a workflow and tessa can pick from the variety of workflows that are available already in that system so it's just to pick one here from that list and the configuration of the action plan is complete tesla can take a view on the workflow that has been started automatically by using the workflow tracking which it gives an overview about the currently on-time workflows it also has additional filtering options so the completed workflows could also be displayed with quite simple here and for the current workflow we are seeing that it's at the id card return step assigned to tessa she can also see the the previous step as well as the future steps this workflow will take and the scanned document is also attached here to that workflow in extended ecm all information is centered around the workspace so if you're looking at the employee workspace for udo fogle we'll then also see here both the document the checklist that has been sent out as well as the the captured and returned checklist here in that employee workspace and this is concluding our end-to-end demonstration