Journey designer question
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-29-2024 05:19 AM
Hello! I am a trainee exploring Journey designer and would appreciate an advice please! I am trying to configure the Journey Designer in a demo instance and one issue I am having is that when a Manager persona requests a Journey in EC via a record producer, after filling the form with new employee (from demo database) details, the journey is created. But! The system ignores new hire person's details and creates a journey for the requesting manager as new hire, owned by the same manager!
I can't figure out why this happens and which setting is responsible for this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-29-2024 06:57 AM
Check on your variables: what are they mapping to? Is requested by/requested for mapped to the same user?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-29-2024 08:52 AM
Thanks, Mark! Unfortunately, none the wiser still. For extra context, I have 2 New Hire Onboarding Record producer items on EC for 2 slightly different onboarding user groups. One was based on demo version from Employee Experience onboarding pack that I uploaded from SN store. That one is working as intended. Another one that is having an issue described above was pretty much copied from the demo one, so should have all the settings and mappings already there really without me configuring anything additionally. I only restricted it to a specific group under Available for. Otherwise, it is largely the same. So I dont really understand why the form is working this way that it chooses the subject person the same as Journey Owner. Can you direct me where I can look into mapping the Subject person?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2024 02:12 AM
You say 'should have all the settings and mappings'. Is that confirmed?
You say 'otherwise, it is largely the same'. What are the other differences?
Your variables are probably setup to map to a field? Or is it scripted to map them? If it's the first: check to which fields your variables are mapped (on the form of the variable itself). If it's the last: check what the script says to map on those variables.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2024 10:02 AM
Unfortunately, I've been going round in circles trying to figure out the difference that is causing the issue, between the two Record producers: (one -New Hire (Demo)) that was provided as part of the Employee Experience Pack: Enterprise Onboarding content that I uploaded as an Update set from store) and the one that I copied from that Record Producer in an attempt to create another variation. One that came as part of the pack from store works well and maps First Name and Last name of a new hire persona (entered via Record producer form in EC) as Employee to a Lifecycle Event case. However, my copy of the pack's record producer does not create the journey for an employee. It carried over all settings and mappings so appears the same in that context = all 25 variables etc). Variables are not mapped to a field, there is a script. Both Record Producers have the same script (naturally, as mine is a copy).