spolen - Wednesday, April 23, 2008 11:22 AM:
On previous ECR's that have been approved, we have never had to use a password as that is the way the consultant set our configuration up at start up. But now I have an ECR that is being disapproved, and the system is asking for a password, and we don't have one and have never had to use one in any of our Change Management tasks. Is there a way to remove this requirement? This only happens when disapproving.
Thanks,
Sue
Anonymous - Wednesday, April 23, 2008 11:43 AM:
The password it is asking for is the password you use to log into the system. It is used as a mechanism to "sign" the vote.
To disable this feature, you simply have to edit the Workflow Map and change the Disapprove path from Authentication=Password to Authentication=None.
-Chris
spolen - Wednesday, April 23, 2008 12:38 PM:
I did what you said and changed the path to none, and even logged out and back in the the authentication password property is still active. I even tried using the login password for the system, and that did not work.
Don't have any other ideas do you?
Anonymous - Wednesday, April 23, 2008 1:28 PM:
The workflow map is like a template. The changes will only be reflected in new ECR workflow processes. Existing ECRs were created from previous workflow map, and still contain the old rule.
-Chris
spolen - Monday, April 28, 2008 12:45 PM:
Is there any other way to release this? I understand that from now on it will not need a password to disapprove, but it's in limbo now, and don't want to leave it as open. Should I cancel the workflow? But if I cancel the workflow, I don't know how to show it as closed when researching disapproved ECR's. Any idea's would be helpful.
Thanks Chris,
Sue
Anonymous - Monday, April 28, 2008 1:24 PM:
Sue,
I'm not sure I undestand. Is your login password being rejected?
Are you using integrated Windows Authentication?
-Chris
spolen - Tuesday, April 29, 2008 2:57 PM:
Yes the password is being rejected and yes on integrated Windows Authentication.
Sue
Anonymous - Tuesday, April 29, 2008 5:39 PM:
Okay, this makes a little more sense to me now. The documentation on Windows Authentication mode warns that this can happen and recommends that the workflows be adjusted to use esignatures, which can be set by the users.
Since you are already in the middle of the problem, I can give you this SQL:
update innovator.Workflow_Process_Path
set authentication = 'esignature'
where authentication = 'password'
From your previous posts I can see that you may just want to get rid of signing alltogether. If that is so, please use this SQL:
update innovator.Workflow_Process_Path
set authentication = 'none'
where authentication = 'password'
To other users: I do NOT recommend using these SQLs if you are not in the middle of the exact same problem.
The change may not be reflected until the users log out and log back in with a "backdoor" change like this, but I am not sure offhand.
-Chris
spolen - Thursday, May 1, 2008 8:00 AM:
Thanks Chris,
The SQL worked for removing the requirement for Authentication for the ECR. We are such a small company I can see where this is useful in larger companies, but when we originally had the start up for Innovator, we had requested the customization of no passwords or esignatures to approve/disapprove our changes, so this really helped.
Again, thanks for your help!
Sue
