have you tried capturing value of z1D Action when name is supposed to be inserted? Your filter is probably triggered correctly, but its Run If Qualification isn't matched which is why its Else Actions branch is taken, so you could add message action to Else Actions and have it display value of z1D Action to be recorded in filter log; since you'd be changing filter, you should be able to prepare work info for submittal from Service Request, quickly save modified filter, submit previously prepared work info from Service Request and restore filter to its previous state within a few seconds, so the whole process shouldn't cause disruption even if undertaken on a live system. I suspect that first part of qualification ('z1D Action' != "CREATE_FROM_REQUEST") is causing it to "misfire" because z1D Action is equal to "CREATE_FROM_REQUEST".
If you have any good example how I can modify my filters could you please provide those details so that I will try to work on it further.
You don't need to add field and filter to SRM:WorkInfo because there is already Full Name (1000000017) which is automatically populated by filter SRM:SWI:SetFullName when public worklog/workinfo is created in fulfillment application or when one is submitted in service request, so try displaying it instead.
As mentioned before, when workinfo is added from service request, synchronization with fulfillment application is started and z1D Action is set to "CREATE_FROM_REQUEST", which is why filter you've added to populate zSubmitterFullName isn't triggered -- it specifically checks that 'z1D Action' isn't "CREATE_FROM_REQUEST".
With that and my previous post in mind, I think it would be best to:
- create a copy of Full Name (1000000017) field from SRM:WorkInfo into application's worklog form (HPD:WorkLog) or adjust zSubmitterFullName to match
- replace column in worklog table in HPD:Help Desk with Full Name if new field was created, update it if not
- create filter analogous to SRM:SWI:SetFullName (e. g. HPD:HWI:SetFullName) associated to HPD:WorkLog, executed on Submit and Modify events at 1000, which when 'Full Name' = $NULL$ performs Set Fields action to fetch Full Name from CTM:People where 'Remedy Login ID' = $Work Log Submitter$ into Full Name in HPD:WorkLog -- feel free to reuse old filter, of course
Not only would this achieve your goal, you'd also end up with virtually identical part of workflow in both/all applications.
1 of 1 people found this helpful
Matthew used to work with me so I am aware of this build.
We also made updates to the OOTB filter:
We added a Set Fields firsts action that looks up the Full Name on CTM:People and sets the value in WL Submitter Name.
Then that field is added to the OOTB Push Fields action on that same filter.
Are you certain that is everything you've modified? It does cover manually created worklogs and (probably) those generated by RBE, but neither of two filters which are used to synchronize worklogs (INT:SRMHPD:WLG:CreateWorkInfo_700_Request`! and INT:SRMHPD:WLG:CreateWorkInfo_700_Request1`!) via HPD:IncidentInterface can be triggered by synchronization with worklog originating from SRM:WorkInfo (e. g. when it is entered by customer in SRS:RequestDetails) because in that case z1D Action is set to CREATE_FROM_REQUEST before their execution order.
I will give it a shot and let you know where I landed.
Thanks a lot for your time and help as always.
I would also vote for populating the full name field once and sync it up with other records when the WInfo record gets synced by just adding the field mapping. No need to repopulate. One issue though here is that, as name is stored in regular fields so if name changes, new name won;t reflect.
The alternative could be just to replace the column value with full name by replacing it with a table loop and fetch name from people form when Winfo record is displayed. Some performance hit though if WorkInfo records are too many.
I would create a generic FILTER on Submit which will set Full Name of user from People form based on the login id (Irrespective of source of work info (MyIT/SRM/INC/RBE etc), system will trigger it on EVERY new workinfo creation.