Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.

Why does pp!initiator in Subprocess does not pick the user who triggered the Parent process each time.

Certified Associate Developer

currently I have a subprocess that uses pp!initiator to get the user data to check few validation, and one sometimes the pp!initiator seems to not pick the user from the parent process and i think instead it picks the masteruser (i.e. ABC) which was used to publish the process model.

It happens on random instances. Am i missing something.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    pp!initiator behavior in a subprocess depends on how it's invoked. Sync (Sub-Process node) inherits the parent initiator correctly, while async (Start Process smart service) resolves it to the process model publisher instead. Without a detailed process design view, the exact cause can't be confirmed. Make sure you are not running sub process or node as run as whoever designed this process model under assignment tab.

    Either way, avoid relying on pp!initiator for user validation in subprocesses;  pass the parent initiator explicitly as an input process variable instead.

Reply
  • 0
    Certified Lead Developer

    pp!initiator behavior in a subprocess depends on how it's invoked. Sync (Sub-Process node) inherits the parent initiator correctly, while async (Start Process smart service) resolves it to the process model publisher instead. Without a detailed process design view, the exact cause can't be confirmed. Make sure you are not running sub process or node as run as whoever designed this process model under assignment tab.

    Either way, avoid relying on pp!initiator for user validation in subprocesses;  pass the parent initiator explicitly as an input process variable instead.

Children
No Data