RainerVM's Posts

Hi Tanvirao, that's right, because the actions are not part of the plugin, they are written by myself and as mentioned I attached them to the community post. As the isValidVcoLogin-action you have to download them from my earlier community posts and import them to vco. Rainer

Hi Tanvi, where is your manager defined? In the LDAP-User-Object of the workfow running user (the requester)? Or do you have a special database where you have defined the managers for specific requesters? Rainer

Hi Tanvi, we had a similar problem, and I found a working solution for us maybe you can use it, too. We have a workflow which will be executed from a Requester (which only has the rights to execute this single workflow, no loginrights to vCenter), but because of the running credentials of this workflow it is not possible to create VMs within this workflow. The trick is to start a second workflow with other credentials (enough rights to execute other workflows in vCO and rights to create VMs in vCenter). Therefore I made an "User interaction" in the "Requester"-Workflow where the Operator has to put in his credentials to run the second workflow. To check if the credentials are valid I wrote the attached action. This action has two input parameters (LoginCredentials and the LdapGroup to check if the user is member of). If the given login user is member of the vCO-Administrator-Group or member of the given LdapGroup, the action results true otherwise false. The action has one known issue: If you have a multi domain environment (as we do) and accounts with the same name you will get true also if only one of the users has the needed rights. To use that action to validate the user in the "Request"-workflow, you should use the "Custom validation"-property, the only problem is that you have to create it on an other field than the credential input, because it is not available in vCO on a credential object The value could be like this: ( GetAction("com.alstom.vco4.basic","isValidVcoLogin").call( #operatorCredential,#securityGroup ) ) ? true : "Credentials are not valid." I hope that helps. Best regards, Rainer

Hi Angela, sorry this works also not, because during the execution of the workflow there is no endDate available. And doing the same with the startDate doesn't work either, because it could be that another workflow has been started a view milliseconds later than the current, then I would get the other one and not the current running. But I found a way to get the current workflow token by myself, a bit tricky but it works For everyone who is interested in - here you will find the code of an Action (I called it getCurrentWfToken): Input: none (but must be used within a workflow) Output: WorkflowToken of the current running workflow var objWfToken = null; try { var strAnswerUrl = workflow.getAnswerUrl().url; var strWfTokenId = strAnswerUrl .replace(/^(\[\s\S]TokenId=)|(&returnUrl\[\s\S])$/g,""); objWfToken = Server.findForType("WorkflowToken",strWfTokenId); } catch (objErrMsg) { System.error(objErrMsg); } return objWfToken;

Hi Angela, thank you for your fast reply, but no that's not what I'm looking for, to get the workflow execution list (WorkflowTokens) is no problem (using a Action or the 'User interaction' all possible). My problem is to know which single token of these listed tokens is the token of the current running workflow.