Skip to main content

NetIQ IDM - Start workflow from policy and catch error



Those who want to avoid slowness of designer UI, use XML editor for fast delivery of code by providing following xml stub for start workflow :-)



<do-start-workflow id="$local.sub.etp.resource.UserId$" time-out="30000" url="$local.sub.etp.resource.Endpoint$" workflow-id="$workflow-ldap-dn$"> <arg-password> <token-local-variable name="local.sub.etp.resource.Password" /> </arg-password> <arg-dn> <token-local-variable name="lv.user.ldap.DN" /> </arg-dn> <arg-string name="Product"> <token-local-variable name="lv.group.ldap.DN" /> </arg-string> <arg-string name="Accounts"> <token-local-variable name="lv.user.ldap.DN" /> </arg-string> <arg-string name="Subscriptions"> <token-local-variable name="local.sub.ctp.Subscriptions" /> </arg-string> <arg-string name="IssueTicket"> <token-text xml:space="preserve">N/A</token-text> </arg-string> </do-start-workflow>


to catch the error use following condition with local variable  error.do-start-workflow


<do-if> <arg-conditions> <and> <if-local-variable mode="regex" name="error.do-start-workflow" op="equal">.+</if-local-variable> </and> </arg-conditions> <arg-actions> <do-trace-message level="3"> <arg-string> <token-text xml:space="preserve">Workflow Error Detected PLACEHOLDER</token-text> </arg-string> </do-trace-message> </arg-actions> <arg-actions /> </do-if>

Comments

Post a Comment

Popular posts from this blog

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...
1 comment
Read more

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...
Post a Comment
Read more

Reading Component type attribute values such Email Address

Read Email Attribute from Group: < do-set-local-variable name = "local.sub.etp.MailboxEmail" scope = "policy" > < arg-node-set > < token-src-attr class-name = "Group" name = "EMail Address" > < arg-dn > < token-local-variable name = "loca.sub.etp.Group" /> </ arg-dn > </ token-src-attr > </ arg-node-set > </ do-set-local-variable > This would do following Output: < nds dtdversion = "4.0" ndsversion = "8.x" > < source > < product edition = "Advanced" version = "4.5.6.0" > DirXML </ product > < contact > NetIQ Corporation </ contact > </ source > < output > < instance class-name = "Group" qualified-src-dn = "/N/A" src-dn = "/N/A" src-entry-id = "1...
Post a Comment
Read more