Hi, One of the client is using Documentum and they are managing a scenario like,

In Appian, the task will be shown only when logged in.. Still if you want the task to show the message, you can use confirmMessage attribute of both the buttons to display the message, upon clicking Ok, you can show him a screen to provide username and pwd.. May be this is the only approach I think you could follow to achieve that behavior..

Hi Mohan, I would like to add to nellimaj's comment. I would suggest using a SAIL wizard. In the first form, have the task form with Approve/reject button. You can have confirmMessage attribute set to the Approve/Reject buttons. On the next form, have two components: a textField - for username and a encryptedTextField - for password.

Your SAIL code will look something like this:
load(
local!option: 1,

choose(

local!option ,

a!formLayout(
/*Your task form SAIL code goes here.. */
),

a!formLayout(
/* SAIL code for username and password*/
)


)
)

What would you DO with the username and password the user provides in the form? Achieving this feature apart, I would like to understand what you intend to do with the collected data? i.e. verify it against another system etc.,??

Hi Satya, as per my information, they have a feature in the existing product for signing off any task before completion and they are using this feature in current workflow. Saying it’s just kind of double check of authenticity. Verify against same system.

@mohanp, if that is the case, you can check correctness of username based on loggedInUser but validating the corresponding password.. I am not sure how we can achieve it..

Okay, the fact that a user has logged-in indicates that the user is a valid user. I don't know which other system we are talking about - but in Appian, a task is assigned to a user or group and once you take that task, it changes the ownership to the user. The ownership, controlled by the Appian security model, indicates the fact that the user is the right person to do the job. The audit log is going to hold the information on who completed the task etc., So, the need for user entering the credentials again is not only redundant, it is actually not a best practice. So my recommendation is to re-engineer this part and use Appian security and audit log to hold the required information.

In the past we have used an encrypted text field and an expression rule that hashes a PIN/password for a user and stores it in the database. This solution is not perfect or 100% secure for a number of reasons but it was the best we could come up with given our requirements.

Not sure if it is up to date or not, but there is a shared component that may meet this use case: forum.appian.com/.../summary