Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
6 subscribers
Views
2386 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
I have a process with one node to post an event to news feed. process initiator
venkats533
over 10 years ago
I have a process with one node to post an event to news feed. process initiator has very limited access to the process including news feed. So, I did not give permissions to the news feed to the group who will be initiating the process. The node to post an event to news feed is failing because of security. So, I have configured that node to execute as process designer instead of process initiator. So far so good. When this application is migrated to production environment, an Appian admin account is used to import the package. I have recommended to create a system user account some thing like "Deployment Engineer" and use this account to import the package. Since this will increase the number of users for license purpose, the organization went ahead with using the real person account as administrator to import the application. The production environment is synced with LDAP for authentication. So, when this individual ...
OriginalPostID-140673
OriginalPostID-140673
Discussion posts and replies are publicly visible
Parents
0
Stefan Helzle
A Score Level 3
over 10 years ago
From my experience deactivating users in sync with LDAP can create a lot of trouble. I think creating a process to deactivate users is a better way. This process could handle several scenarios like still active tasks, model ownership, admin groups membership and so on. This process could be started when the user gets deactivated in AD.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Stefan Helzle
A Score Level 3
over 10 years ago
From my experience deactivating users in sync with LDAP can create a lot of trouble. I think creating a process to deactivate users is a better way. This process could handle several scenarios like still active tasks, model ownership, admin groups membership and so on. This process could be started when the user gets deactivated in AD.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data