Appian Data to be accessed by non-apian users

I have a requirement where a non-Appian user needs to access data in Appian system either through SAIL form or in any other way and provide his/her inputs against the each field of Appian data which I need to capture
back into Appian system. I have studied about Embedded Interface but as per my understanding it also requires to enter Appian credentials for accessing the Embedded Interface. Can anyone suggest me the best approach for achieving this requirement. Thanks in Advance

  • Like the others replying to this thread I don't see the benefit to having them not be Appian users, especially since if I understant licensing correctly there's no additional charge for the extra users.

    I do however, see significant detriment to attempting to allow non-users access to Appian system and data.  Appian is very secure against SQL injection and cross-site scripts and other attacks.  Other interfaces might not be as secure, and adding another layer adds more ways for problems (not only hackers but most likely hackers) to get in.

    How are you going to configure security on the system the users DO have access to and configure security on the Appian process models that system is going to connect to?  If there's a problem with this thing you built, is the problem in the external interface, in the Appian, or in the connection?  Can you afford supporting all 3?  If you made them Appian users, you'd only need to support the one system and they'd already have only the correct permissions at no additional cost.  Why wouldn't you make them Appian users?

  • -

    The licensing model is a matter that should be discussed between the licensee and their account executive.  It’s not accurate, in general, that there is “no additional charge for the extra users”.

    We see sometimes that designs are geared towards “gaming” per users licensing.

    As all Appian consultants would agree, a primary guiding principle of Appian application design is implementing correctly. Users notice when an application is intentionally built in a sub-optimal fashion for the purpose of license rationing.  Without user satisfaction, achieving success with your application can be an uphill battle.

  • Thanks David and Robert for your response. As per my understanding the client has asked for this requirement as it is something related to cost per user accessing the Appian is being charged and so they want to limit the no. of Appian users.

    Use case is - As part of the application only one task need to be assigned to a group of managers who needs to review the data and provide their comments back. 

    As mentioned above, as it is the only task the managers work on, client doesn't want them to be Appian users and also as they are the managers at high level they don't want to put their efforts in logging into any system and were expecting to have  a simple way to provide their comments in the task.

Reply Children

 Discussion posts and replies are publicly visible