Skip to main content
sarathkumr268295
July 16, 2024
Question

Process history showing actor name as Administrator

  • July 16, 2024
  • 13 replies
  • 0 views

Hi All,

In some processes, we can see actor name coming as administrator and for some we can see its coming as the person who started the process. This is occuring for subprocesses. Any reason for this difference in behaviour? Where does this originate from??

13 replies

stefanhelzle0001
July 16, 2024

Did you check the security settings of these process models?

sarathkumr268295
July 16, 2024

Adminstrators group is configured for Administrator and users for viewers

stefanhelzle0001
July 16, 2024

OK. When looking at my own system, the column you are referring to has the title "Object" and does only show the process node, but not the role of the user.

karumurua531442
July 16, 2024

hi [mention:b08a9915dde2428e9c6dfef8cba0cdd6:e9ed411860ed4f2ba0265705b8793d05]  is your sub-process configured as  Run as whoever started the process? could you check your security settings of your PM

sarathkumr268295
July 16, 2024

Yes it is

July 16, 2024
I see the following different values in the Actor column for different processes:
  • Admin (Service Account)
  • System
  • Administrator
  • User( ABCD, XYZ, etc.)

Seems interesting.

Not sure what is the difference between Administrator and system.

konduruc733182
July 16, 2024

How is this process being triggered? Are you using any start process smart service? if yes, is it also being triggered somewhere else in a different way?

sarathkumr268295
July 16, 2024

In one scenario, the sub process is triggered when related action completes and in another scenario, the subprocess is triggered when the workflow completes. During related action flow, we can see the user name and in the other, we can see administrator coming in actor name

mikes0011
Brainy
July 16, 2024

The value will be different depending on how the top-most parent process was triggered as well as what the "Assignment" configuration for the subprocess is set to.  If the subprocess is set to "Run as whoever designed this process model", then regardless of the initiator of the parent process, the initiator of the subprocess will show up as whatever account last published the subprocess (typically your Import Admin service account, assuming you're hopefully using such a setup).  If it's set to "run as whoever started the process", then it'll inherit the "initiator" value from its parent (NOTE: it can only inherit the exact same "initiator" as the parent, there's no avenue by which to change this to any other user).

July 16, 2024

There are a couple of places I've seen "Administrator" come up.

  • If the process model is a feature that is installed by Appian Support (e.g. RWM / RPA, Case Management, Process HQ) or it is a process model that was installed by Appian when creating your environments (which happens on beta environments), and that process model is set to "Run as whoever designed this process", then "Administrator" will be the process initiator. This can also happen if Appian Cloud Support republishes existing process models for whatever reason, but there would be a support case tied to it.
  • It's been a while, but I also vaguely remember some nuance about pp!initiator when the process was started by process to process message receipt.
  • if the process were started by email, you should see ANONYMOUS (as of 24.2).
  • The only other place I've seen "Administrator" is when checking the box to automatically create Appian users during SAML authentication. The audit logs will show "Administrator" as the account which created the user.