Set WorkItem ID in IDM 7

I'm having trouble setting the work item ID in IDM 7. When I set the work item name, it only changes the name value in the work item XML object. The ID value, which is required for links, etc, remains a new unique value generated when the work item is created.
Thanks for your help.
Current code:
            <Variable name='workItemName'>
                <invoke class='com.waveset.util.Util' name='getUniqueId'/>
            </Variable>
            <Activity id='3' name='Result'>
                <ManualAction id='0' name='Show Result'>
                    <WorkItemName>
                        <ref>workItemName</ref>
                    </WorkItemName>
                </ManualAction>
             </Activity>

You can pass <ref>workItemName</ref> as the value of the id parameter in the links It will work perfectly eventhogh your code changes the name of workitem and not its ID.

Similar Messages

Setting Productive password in IDM

I would like to set productive passsword using IDM. According to "Note 1287410 - BAPI_USER_CHANGE: Set productive password" this is now possible.
How do I set the PRODUCTIVE_PWD flag in the ToSAP pass. What is the ABAP connector attribute. Just putting productive_pwd does not work.
Any help is much apprecited.
Thanks
Shabna

Guess you could set an initial password as you do it, as a first step. Then afterwards you call SUSR_USER_CHANGE_PASSWORD_RFC.
Procedure to set a productive password for a user:
1) Call BAPI_USER_CHANGE (set an "intermidiate" and intial password)
2) Call SUSR_USER_CHANGE_PASSWORD_RFC (set your real new password, old password = intermediate from the call before)
I think, we've tried that successfully in the past....
Martin

How to set DEFAULT ORGANIZATION in IDM

Hi all,
something strange here.
I assigned 3 different organizations in IDM to a couple of our Administrators.
Here's the problem : whenever an administrator performs a CREATE action (Creates a new user), for some reason, IDM chooses the third organization as the DEFAULT organization in which to place the Employee.
I intentionally removed the : *<FieldRef name='waveset.organization'/>*
Even then, it's quite weird that IDM would decide for itself which Organization to place a new user.
My question is : is there any way to set a Default Organization in my User Form (or in the Create User Workflow) ?
I tried to do the following in my User Form :
*<Field name='waveset.organization'>*
*<Default>*
*<s>Organization A</s>*
*<Default>*
*</Field>*
But, it did not work. IDM kept selecting another Organization as the Default, and all newly-created users were sent there.
Please, help

Hi MichaelSt
I have modified your code a little based on code I use. See what you think. By the way I have not tested the code.
I do not global for variables that are only used within the form.
<Rule name='Rule for Organization' >
<RuleArgument name='myorganization'/>
    <block>
      <switch>
        <case>
          <s>First Level Org (for regular employees)</s>
          <s>Top:First_Level</s>
        </case>
        <case>
          <s>Second Level Org</s>
          <s>Top:Second_Level</s>
        </case>
        <case>
          <s>Third Level Org</s>
          <s>Top:Third_Level</s>
        </case>
      </switch>
    </block>
<MemberObjectGroups>
    <ObjectRef type='ObjectGroup' id='#ID#All' name='All'/>
</MemberObjectGroups>
</Rule>
<Field name=':variables.myorganization'>
<Display class='Select'>
    <Property name='title' value='Employee Folder'/>
    <Property name='width' value='50'/>
    <Property name='sorted' value='false'/>
    <Property name='required' value='true'/>
    <Property name='nullLabel' value='Select'/>
    <Property name='allowedValues'>
      <list>
        <s>First Level Org (for regular employees)</s>
        <s>Second Level Org</s>
        <s>Third Level Org</s>
      </list>
    </Property>
</Display>
</Field>
<Field name='waveset.organization'>
<Derivation>
    <rule name='Rule for Organization'>
      <argument name='myorganization' value='$(:variables.myorganization)'>
      </argument>
    </rule>
</Derivation>
</Field>

Role assignments not set in ABAP but IdM indicates OK status

Hi,
We went live with IDM 7.2 SP8 last month. We have started to see issues with Business Role assignments in target systems. Generally, BR assignments are parsed to respective privileges and assigned correctly. Sometimes privileges in one target will get assigned but not in another target. Occassionally assigning privileges to one target does not get through either. In all cases the IdM assignment is marked as 'OK', but when we check the backend the assignment is not there. Log entries don't show any jobs triggered for the target that failed to update (and consequently there is no log entries in that target either). But why would IdM mark the specific privilege as 'OK' status -- it should either remain 'Pending' or 'Failed' but certainly not 'OK'.
This effect is inconsistent -- it works correctly at times and fails at others -- increasingly more failures. There is nothing different about the users or environment. We see this in ECC, BW, GTS, etc. We have 36 prd and non-prd systems linked systems. Initially we thought this only affected prd systems as BR's only have prd privileges and the PRD targets are load-balanced. For non-prd systems the assignments are direct privileges, not BRs, and they are not load-balaced. We are now seeing this in behavior in all environments for BR's or direct privilege assignments, in prd and non-prd targets.
Since BR's have appovers we cannot remove BR's and re-assign in production. So for non-prd targets we have removed the privileges, those that indicated 'OK' but did not get set in the target, and reapplied -- the privileges get deleted successfully without any corresponding job being triggered and then when we re-add it the assignment goes into 'OK' status without any job being triggered.
When we tried assigning another user the same privileges it went through fine to the target and IDM marked 'OK' -- exactly as it is supposed to work (non-prod privileges have no approvals).
We are not able to re-produce this in our DEV environment -- the targets are non-load balanced. The assignments work consistently, both BR's and privileges.
Has anyone seen such behavior by IdM?
Thanks for your thoughts.
Ashok

Hi,
Thanks for the suggestion. But ours was a different problem.
The issue was with a faulty reconciliation job that had been fixed. But it had done its damage before the fix and this caused the inconsistent behavior.
During the reconciliation job (to update changed and add new backend roles in IDM) various task trigger attributes get disabled and then re-enabled after the import. These disabled triggers did not get re-enabled for the privileges on some systems. And the reconciliation job was also delta enabled, so only new privileges, after the initial load, should have been impacted. But impact to many privileges -- all privileges of some target systems -- misled our investigation. The timing of the reconciliation job executions kind of added to the confusion and inconsistencies during the initial setup. But we finally tracked this down and wrote a custom job to fix the triggers for only the affected privileges. Assignments to all systems started to function successfully as expected.
Best regards,
Ashok

SET workitem in error status

Hi, i want to force the status error in one workitem. I have one Z objetc, in one of the method of this object i want to return an error to avoid the termination of the workitem. ¿Somo idea?

see, try this...
change the container, remove some mandatory field values. and execute the work item, this will cause the workflow to goto error as some uncaught exception might occur because of this.
or i am guessing that you are using a dialog workitem for now!! if yes, then go inside the debugger for this task method and do some activity some that it will dump
Edited by: Soumyaprakash Mishra on Dec 14, 2011 12:31 AM

Help: Connecting Tomcat to CA-IDMS Using JDBC Type 4 Drivers (JNDI)

Hi there,
I have a rather interesting / complex problem......creating a connection to CA-IDMS from Tomcat using JDBC type 4 drivers (CA provide the type 4 driver).
We have a zSeries 9 IBM mainframe running CA-IDMS r16.1, and I need to connect to the IDMS from Tomcat (running on Linux) using the JDBC Type 4 drivers provided by CA.
At this stage I am struggling with the actual setup and configuration of Tomcats server.xml and web.xml files. These are the files where the JDBC configuration is set (I think). I have to setup the CA-IDMS part of the configuration, but that is a different problem. Basically there is a TCP/IP listener on the IDMS, waiting for incoming connections from the JDBC type 4 driver.
I set up a Tomcat to MySQL connection using MySQL Connector / J, which is a similar kind of process to what I am trying to achieve with IDMS. MySQL connector / J came with a jar file which is placed in Tomcats lib folder, and then the JDBC setup for the web application is created in Tomcat's server.xml and web.xml files. You can then connect to the MySQL database using JSP and the configured JDBC driver / connection. The CA-IDMS Server comes with an idmsjdbc.jar file, which I think is the JDBC typr 4 driver. I think it needs to be placed in the Tomcat /lib folder, but I dont know how to set up the configuration.
There is a JDBC DriverManager which allows JDBC drivers to connect to CA-IDMS. The DriverManager recognises the following syntax:
jdbc:idms://hostname:port/database
This allows the JDBC driver running within Tomcat to connect to the IDMS which is running on the IDM mainframe. CA IDMS r16 supports direct connections from the Type 4 JDBC driver to the Central Version on IDMS. "hostname" is the DNS name or IP address of the machine where the CV is running, and "port" is the IP port that was specified for the listener PTERM (setup on the IDMS side).
There is a caidms.properties file for the JDBC driver, which is used to specify user ID, password, and optional accounting information. It can also be used to specify physical connection information, allowing an application to connect to a CA-IDMS database without requiring the definition of an ODBC style data source. However, I dont know where to place this file within the Tomcat setup.
There is also an IdmsDataSource class. I dont know where to configure this or how to set it up; the CA-IDMS Server manual states the following:
This class implements the JDBC DataSource interface. It is used with an application server (Tomcat) providing Java Naming and Directory Interface (JNDI) naming service to establish a connection to a CA IDMS database. IdmsDataSource properties conform to the Java Beans naming conventions and are implicitly defined by public setter and getter methods. For example, the description property, which is required for all DataSource implementations, is set using the setDescription(String) method. The application server may use the java.lang.reflection methods to discover DataSource properties and provide an interface to set them, or may simply require that they are defined in some configuration file. IdmsDataSource properties are used to specify the connection parameters. These properties are the equivalent of the DriverPropertyInfo attributes described in the previous section and can be used to completely define the parameters needed to connect to a database. Like a URL, an IdmsDataSource object can also reference an ODBC style data source name, where the connection parameters are defined in the configuration file on Linux.
Is there anyone that can try to point me in the right direction to setting up the JDBC connection? I am totally new to Java and so the instructions are not making much sense at the moment. Any help, hints, tips..anything will be greatly appreciated as I have just hit a brick wall here. I can't find much to do with setting up the CA-IDMS Server JDBC type 4 driver online either....if anyone can point me to some resources that would also be extremely useful.
Kind regards
Jp

You say you've managed to get the JDBC driver working
in an application but not in a JSP. You also say that
the error you get is
"com.microsoft.jdbc.sqlserver.SQLServerDriver".
I'd be willing to bet that the exception that you have
got is a ClassNotFoundException. I.E. your application
server hasn't found the JDBC driver classes. The
application server probably doesn't use your current
CLASSPATH to look for classes. It will be setup within
the application server in some way and you'll need to
check your app server documentation to see how it is
done.
Try replacing
e.printStackTrace();with
e.printStackTrace(out);to get a full stack trace of your error.
ColTried it. Got this error when I tried to run the JSP.
Incompatible type for method. Can't convert javax.servlet.jsp.JspWriter to java.io.PrintWriter.
e.printStackTrace(out);
I'm currently using Apache Tomcat 4.0.3 as my JSP/Servlet Container.
I'm also using Type 4 MS SQL Server 2000 JDBC driver version 2.0 on my NT4.0 Server.
Do I need to set my JDBC driver in my container? if so, how do I do that?

How to forward the workitem

Hi All,
I have a requirement wherein we need to send the work item to next high level manager if the person who received the workitem did not respond for 2 days. Also need to make the workitem obsolete for the current user.
Can anyone let me know the proceudre to do this.

Hi Neeraja
Yr Requirement can be solve by using Deadline monitoring and Process control.
For deadlind monitoring refer
http://****************/Tutorials/Workflow/DeadlineMonitoring/DM1.htm
here u have set 2 days deadline . same as in the link u hav to go that Workitem sending Task in that to tab u2018Latest Endu2019
put u2018Work item creationu2019 in time 2 days. Action : Modeled , Out come : any textu201D Deadline monitoringu201D. Then save the task. When u come out in the Workflow template there in the path where the text u2018Deadline monitoring u2019 is written add a
Process control step . there inside that step in u2018function u2019 put : set workitem to Obsolute.
And in u2018workflow stepu2019 : give the no of that step which u want to make obsolute if the dead line is reached. Save it .
Then in the path with text u2018process absoluteu2019 create the same task to sent the Workitem but put the agent as next high level manager.
I think this will solve yr problem. I hav implement it in my Workflow. The requirement was same.
thanks
Kakoli
Edited by: kakoli debroy on Jul 31, 2008 2:49 PM

IDM Mass Operations

Hello everyone,
we're investigating the possibility to deploy SAP CUA or SAP IDM at our Company. We're a little uncertain about the IDM solution because we heard that there might be limitations around mass operations, particularly:
1) Mass changes/Deletes/Lock and Unlock: functionality like that provided by SU10
2) Tool to create users from a template and in mass assignment of roles to users
Could any of you clear this up for me?
Thank you.
Regards

It requires a minimal amount of "coding" and some understanding of how the management console works. This is not an option for regular end users, only for people who are setting up and administrating IdM in the management console.
See screenshots here: http://min.us/mvjtmLg
We have also coded a tool in Java/JSP to interface with the IdM database and allow for mass uploads by a few select end users, but this is very dangerous and I'm not sure I'd recommend it unless you can ensure a certain level of competence on the part of these users...

Delete credit memo work item created in VA01 when the user change value

Hi,
In T.code VA01 Credit memo request is creating, this document will automatically create work item. Based on Net value in credit memo request, the work item should go for 5 levels of approval. After 1st person is approved, the workflow initiator realized that the net value in created Credit Memo request is wrong; he is going to VA02 and correcting the net value. Again we have to create new work item for this and delete the already created work item. Client has clearly mentioned when ever there is change in 5 critical fields in VA02 then only create fresh work item otherwise no need to create SECOND TIME work item. Net value is one of the critical field in the list.
How to track already created credit memo request and how to delete the previously created work item. What is the feasibility of this requirement and how to handle this situation?
Regards
Vijay

Hi,
Just put a Fork and put 1 out of 2 outcomes and in the first alternative, you put your witem that goes to user B. In the 2nd alternative, put a Wait for event "CHANGED". And after this, put a process control step with "Set workitems to Obsolete" or "Cancel workflow" etc., depending on your requirement.
Pl note that this will only take out old witems, but you need to send a new witem for which you need to trigger another instance of the workflow as well. pl put CHANGED event also as one of the triggering events and use condition editor to restrict the fields that triggers the workflow.
Also, look into the IMG config of the following path. This might be a fitting solution.
In SPRO, go to Financial Accounting (New)---> Financial Accounting Global settings(New) -
>Tools --->Workflow ---> Workflow for Document Parking -->Reset Release Approvals(Customers).
Here, you can list down the fields, the workflow should restart. But, then you need to give the workflow details etc., in the relevant config settings.
We have used this in restarting workflows for General Ledger(GL) documents' workflow when some important fields are changed.
For this config settings, look into the following help link.
http://help.sap.com/erp2005_ehp_02/helpdata/en/01/a9cdd8455711d182b40000e829fbfe/frameset.htm
Hope this helps.
venu

Roles are not saving in idm6.0

hi everybody,
in my create user workflow i am getting the all the details from a form and then creating a view and then setting the idm atributes with the form values and then provisioning .
my problem is i could not able to set the role in idm.
my code is :
<set name='user.waveset.roles'>
<ref>roles</ref>
</set>
where roles is the form field value .
the allowed values of the field are contractor,manager,employee.
i select one role in the form and while setting the idm attributes i am assigning the role to the user.waveset.roles.
but when i checked in the idm interface all the fields like accountid ,firstname,lastname,email and password are set but in the assignment section Role is not assigned .
please can anybody tell me where i am wrong .
thanks a lot if anyone can solve this problem

Hi,
try to set the role by the following way,
<set name='userView.waveset.roles'>
<appendAll>
<ref>userView.waveset.roles</ref>
<ref>roles</ref>
</appendAll>
</set>
hope this might help you.
Regards,
Ashok

Approval process should proceed if deadlins is missed

Hi all,
In the workflow WS10400002 (One-step approval) in SRM, when the deadline had exceeded the approval should happen automatically.
While checking in the latest end tab, an alert mail can be triggered. but how do we make sure that the approval process happens automatically if the deadline is missed.
Thanks and regards
Kishan

In the Latest End tab you need to make a Modelled deadline not a Display Text. If modelled deadline is done you have to name an outcome that branches out from the task where deadline is set. Now you use this step to complete the approval step automatically and after that create a Process control step that will complete the Workflow.
Just follow the steps
1)You can use Latest End Tab in a Step which is attached to a task. Use Modelled deadline. Using this another branch is created from the step.
2)Activate the Outcome Processing obsolete for the Step that needs to be sent to the Manager.
3) Now put a process control in the branch that has been created due to modelled deadline. Use "Set Workitem to Obsolete" in the Function and provide the Step number in which the deadline step is incorporated.
4) Now create another step at the branch Processing obsolete of the step that has the deadline and copy the above step with deadline removing the deadline part. This step is only for manager.
use this accordingly in your Workflow.
<b>Reward points if useful</b>

Work Item to be disappeared from user1 inbox when escalated to user2

Hi,
I created a customising workflow for Credit Memo Request with 2 escalations for approval. I have used Fork operation to get this functionality with Requested start option in 2nd and 3rd branch to escalate after 3 and 6 days respectively if not the document is approved by the agent in branch 1.
Every thing works fine, but the client wants the work item to be removed from USER1's inbox when escalates to USER2 and from USER1 & USER2's inbox when escalated to USER3.
Could you guide how can we do it in my case.
Thanks in advance.
Edited by: Jaya on Sep 30, 2010 10:26 AM

HI Jaya,
you can make use of 'Processing Obsolete' here as it would remove workitems from the approvers inbox whose deadline is missed.
First of all , in the decision step make 'processing obsolete' active under 'outcome tab' of the task.
Use latest end with time as 3 days and action as modeled.Now in modeled deadline, make use of process control step and select 'set workitem as obsolete' and put step number of your dialogue step in 'workflow step'.
This will make the workitem diasppear from the approver inbox once the deadline is missed after 3 days.
Now to repeat the process fro 2nd and 3rd approver , put all of this in a loop, and before loop ends, find the next approver id in the outcome 'Processing obsolete' of the desicion step.and pass this id to the expression used for approver.
The loop condition can be a flag that is set to X when a deadline is reached. To do so, add a container operation in modeled deadline before process control step that will put the flag X.
So loop will continue to second pass if deadline is missed and hence so on till 3rd approver.Formulate condition for highest level of approval too.
Hope this helps.
Regards,
Sangvir Singh

AD connection and repository population

Ok, so I am a newbie to the SAP IDM space, but am well versed in LDAP and other IDM solutions. I need some help for the scenario we are working on Password change replication from AD to SAP systems.
AD has the
users and will be the source for passwords
SAP systems are existing
We do not use SAP
HCM, thus the user source is AD.
So, we started by setting up the SAP IDM on windows, with an Oracle DB.
We have a dispatcher, and it says its running
I setup a repository for AD
I tried setting up a couple of jobs to populate the repository, but dont get anything.
I assume I am missing something - i havent configured something.
Any help would be appreciated.

Hi Jeremy
Start with the tutorials first.
Somewhere in your IdM Installation folder or your setup folder there's a Tutorial folder.
There's one tutorial for LDAP-Tasks which could help you.
Also there exist some installation-related PDFs that help you during initial configuration.
On the other hand you should install the "SAP Provisioning Framework" which contains Tasks for commonly used SAP-related systems (ABAP, Portal, LDAP, ADS and so on).
If you search service.sap.com there exist also 2 important PDFs about how to use the SAP Provisioning Framework and the expected system landscape ("Identity Management for SAP System Landscapes: Architectural Overview" & "Identity Management for SAP System Landscapes: Configuration Guide").
Hope I could help.
Regards
Michael

ESS/Leave Reqest Workflow Problem Still in Process when Escallated

Helo Every one,
My leave request workflow is Zworkflow which is working fine in the production.Recently in the last month business request for escalation of leave request when direct manager not approved with in the time frame.
So i added latest end to the Approve task which uses the ABAP class CL_PT_REQ_WF_ATTRIBS and Method Dummy.
So the task has 3 outcomes one is deadline reached,process obsolete and processed. and after that i added a loop which will create new work item when escalated.
When i apply a leave on the portal the workflow is triggering and stopping in the Approve step in the log which is fine and when i with withdrawn the leave without any escallation it is taking one of the brach Processed which i mentioned above and reaching to the event and completing the workflow which is 100%.
When the direct manager doe'nt approve then it is escallating to the next level manager which is fine.Once the escallation happen and the leave is withdrawn by the Employee(Initiator) then it is not taking any of the 3 paths which i mentioned above and not reacting at all.But the status in the workflow container REQ.STATUS is changing to "WITHDRAWN".
The same thing is happening for the APPROVE once escallation happens.It keeps on escallating even the leave is approved and posted in the database.
Please reply me if you are not clear.
Thanks,
Raja.

Hi Raja,
Here is how I can think of, based on your requirement.
I hope you are using modelled deadline. Have the process control step in the deadline branch with function set workitem to obselete. This makes the actual work item to obselete everytime it reaches the deadline and make it create one with an escalated agent. And also keep the dialog task in the loop.
Hope this helps.
Thanks,
Raj

Probelm with decision step type

Hi,
I am using the decision step type to display release and reject the options to the approver . i am using the latest end tab to escalate( forward) the workitem to next available approver .( deadline monitoring 30 min) .
workitem is generating in the 2nd available approver inbox after 30 min . but the same workitem is still available in the 1st approver inbox ( of course it display the message the following deadline was missed and latest end reached) .
But even after the 2nd approver gets the workitem in his inbox ,the 1st approver is able to execute the same workitem by ignoring the message .
Please can any one explain me what is reason behind this.
Please can any one helping me how can i delete the workitem in the 1st approver inbox once the workitem is created in the 2nd approver inbox .

Just follow the steps
1)You can use Latest End Tab in a Step which is attached to a task. Use Modelled deadline. Using this another branch is created from the step.
2)Activate the Outcome Processing obsolete for the Step that needs to be sent to the Manager.
3) Now put a process control in the branch that has been created due to modelled deadline. Use "Set Workitem to Obsolete" in the Function and provide the Step number in which the deadline step is incorporated.
4) Now create another step at the branch Processing obsolete of the step that has the deadline and copy the above step with deadline removing the deadline part. This step is only for 2nd approver.
<b>Reward points if useful</b>
Thanks
Arghadip

Set WorkItem ID in IDM 7

Similar Messages

Maybe you are looking for