Self-Register User Notifications

I need to send out several email notifications during a self-register user request: Request Initiated, Request Awaiting Approval, Request Approved/Rejected. It seems that OIM 11g/SOA is only setup to handle 2 out of these 4. The SOA engine can notify the approver of the pending approval. OIM can notify the end-user that the account was approved and created based on the Self-Register User Event. Unfortunately, there doesn't seem to be an OIM event or enough data passed to SOA to handle the Request Initiated or Request Rejected scenarios. I am wondering if anyone knows of a way to meet these requirements?
Thanks,
Pete

Here is a solution but will work only if users click on the appropriate self registration links. Also may not be very feasible in cases where self registered user need to be added to a group from large number of groups.
In the workflow step did you configure multiple targets?
You can configure multiple targets under the workflow domain you have chosen.
To self-register a user under a particular group you need to provide a self registration link to users with ObDomainName query string configured appropriately.
Eg:
Self registration Workflow domain is dc=acme, dc=com
Say you want users to be added to groups
cn=users1,dc=acme,dc=com and
cn=users2,dc=acme,dc=com.
For this create 2 Targets in 2nd step of your workflow for the two groups you want user should be added to. Now you have effectively two self registration urls,
http://host:port/identity/oblix/apps/userservcenter/bin/userservcenter.cgi?program=workflowSelfRegistration&ObWorkflowName=...<your value here>...&ObDomainName=cn=users1,dc=acme,dc=com
http://host:port/identity/oblix/apps/userservcenter/bin/userservcenter.cgi?program=workflowSelfRegistration&ObWorkflowName=...<your value here>...&ObDomainName=cn=users2,dc=acme,dc=com
Now if you can manage users to click on appropriate links then you can achieve the goal.

Similar Messages

  • Self Register User Auto Approval Scenario in OIM 11g

    Hello,
    I was working on scenario of suppressing approval while Self-Registrating user, following steps were performed
    1) Export SelfCreateUserDataSet.xml using weblogicExportMetadata.sh
    2) Modified SelfCreateUserDataSet.xml [removed approver-only tag from organization attribuite]
    3) Imported SelfCreateUserDataSet.xml using weblogicImportMetadata.sh
    4) Restarted OIM & SOA server.
    5) Created approval policies i.e. Request Level & Operational Level bote with Auto Approve condition.
    6) Made a clone of Self-Register User template & added organization restriction & added Self Operator role.
    7) When tested above scenario then xelsysadm had to approve for request & operational level,organization was already selected ,so shouldnt it get approved
    automatically as i have mentioned Auto-Approve in approval policy ?
    Tested using following link:
    http://hostname:port/oim/faces/pages/USelf.jspx?E_TYPE=USELF&OP_TYPE=SELF_REGISTRATION&T_ID=Clone of Self-Register User
    Thanks,
    Rahul

    Hello,
    No i cannot see organization field as i have restricted organization to 'xyz' .
    My Issue is resolved & problem was that i had changed password of OIM,weblogic also updated boot.properties file in oim & soa,but for some reason my SOA was not working although SOA server was running,so changed password of SOAADMIN from EM,restarted all 3 servers & now my scenario of Self Register Auto Approve works.
    Now only thing i am curious is that when i self register user,it shows Request failed,but when checked in OIM user is created .
    Thank-You
    Rahul

  • Self-Register user workflow add user to Group

    Hi,
    I have a fairly basic Self-Register user workflow that I am playing with in OAM. I am wondering if I can somehow add a step(s) into my workflow that will add the user to be a member of a Group in OAM during registration?
    If so, can this be done without an "external action" or custom code?
    If anyone knows anything that can help I'd appreciate it.
    Thanks,
    Jackie

    Here is a solution but will work only if users click on the appropriate self registration links. Also may not be very feasible in cases where self registered user need to be added to a group from large number of groups.
    In the workflow step did you configure multiple targets?
    You can configure multiple targets under the workflow domain you have chosen.
    To self-register a user under a particular group you need to provide a self registration link to users with ObDomainName query string configured appropriately.
    Eg:
    Self registration Workflow domain is dc=acme, dc=com
    Say you want users to be added to groups
    cn=users1,dc=acme,dc=com and
    cn=users2,dc=acme,dc=com.
    For this create 2 Targets in 2nd step of your workflow for the two groups you want user should be added to. Now you have effectively two self registration urls,
    http://host:port/identity/oblix/apps/userservcenter/bin/userservcenter.cgi?program=workflowSelfRegistration&ObWorkflowName=...<your value here>...&ObDomainName=cn=users1,dc=acme,dc=com
    http://host:port/identity/oblix/apps/userservcenter/bin/userservcenter.cgi?program=workflowSelfRegistration&ObWorkflowName=...<your value here>...&ObDomainName=cn=users2,dc=acme,dc=com
    Now if you can manage users to click on appropriate links then you can achieve the goal.

  • Populate fields only for self registered users

    Hi All,
    Scenario : I have an approval task for self registered user. When the user enters the details it goes for approval. The userAccount gets created only when the approver enters values for mandatory attributes like organization.I also have few other mandatory attributes that needs to be filled out.
    The requirement is that these mandatory fields have to be populated automatically. I cannot use an entity adapter because if i do so the manadatory fields will be populated when users are being created by xelsysadm.Please help.
    Thanks.

    You can use Ajax or Java Script for populating other fields.

  • Allow creation of Self Registered Users

    Under Portal Settings in the Admin section is a checkbox to "Allow creation of Self Registered Users". And a note that says "Changes in these settings will take effect immediately."
    I'd like to utilize this feature and have therefore checked the box, and made sure my custom login adaptive layout includes this tag: <pt:ptui.createaccount />
    After giving the setting a good hour to work its magic, the view source shows that the tag creates just this: <span id="pt-login-create-account"></span>
    I was assuming that there'd be some more code than that - at least a link!
    Any idea what might be the issue? It seems like such a straight forward type of setting.
    Thanks

    The issue has been narrowed down slightly by including the problematic extranet login page as a portlet within our intranet - which then succeeds in displaying the page.
    One item of note was that we have the admin area installed on both of our load balanced intranet servers - and each had to be set to allow creation of users via the admin interface before it could be seen by all. This is slightly disconcerting as we assumed they relied on the same data repository (db).
    Fortunately, this might be a clue as to why it isn't working still on our extranet server.
    The catch there is that we can't access the admin interface via our extranet - so I'm now in the process of trying to track down exactly where this value is saved to from the project settings page.
    Any suggestions?
    Thanks!
    Solution--
    I set our extranet to be able to display the admin section, restarted the server, logged in, checked that the admin setting was correct, reset the config file, restarted the portal and then the link magically appeared.
    Lesson learned - don't trust the documentation when it says that a restart isn't required...

  • Self-Register User Template Error : MinLimitException: size minimum limit

    I am using OIM 11.1.1.5. When I click "Self-Register User" request template link, I get the following errors. Note that this link was working on other OIM environment where no custom UDFs are present.
    Thanks!
    Kabi
    The Error in IM pop up screen says "size < minimum limit ; ADF_FACES-60097: for more information, please see the server's error log or an entry beginning with ADF_FACES-60096:Server Exception during PPR,#1"
    The oim_server1-diagnostic.log says
    ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase INVOKE_APPLICATION 5[[
    oracle.iam.platform.utils.MinLimitException: size < minimum limit
         at oracle.iam.platform.canonic.model.Values.setMinLimit(Values.java:187)
         at oracle.iam.requesttemplate.agentry.operations.OpenActor.renderAttributeRestrictionsTab(OpenActor.java:822)
         at oracle.iam.requesttemplate.agentry.operations.OpenActor.prepare(OpenActor.java:195)
    ---------------------------------------

    Did u import any object for self registration? if so import it again...i have seen this error before in my env.
    If the self registration fails, then it is a Oracle Bug and they are working on getting a patch for it...
    ~VSN

  • Problem while creating self-registered users

    Hi
    we are creating a self registered users. When the self registered users enters the data it has to go for the line manager approval.
    We have an entity adapter which is triggering after the manager approval. What the adapter will do is it triggers an end date for the user after the approval.
    But its showing "DOBJ.error Create user" error after the approval.So we are not able to create the user
    KK

    I am providing all the mandatory values like Organization and last name.
    But still its throwing DOBJ error.
    Any Clue...
    At this moment i am not able to provide the logs.
    Thanks,
    KK

  • Where do the self registered users go

    Hi ,
    I am new to oracle web center. i have created a sample app no db connections just pure oracle web portal application.
    This app has a defalut weblogic/weblogic1 admin user.
    Apart from this i ahave also added a self registration page from the readily available security taskflow.
    Now i am able to add users at runtime through this self registration page.
    But since i am not using any DB am wondering where are these newly registered users and their passwords are being persisted.
    can any one shed some light on this cos i cant even see the new users in Jazn xml
    --Sanket                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    ok these registered users are being created in the integrated weblogic ;
    but why arent we able to browse thorugh thtem trough jazn xml.
    --sanket                                                                                                                                                                                                                                                                                                   

  • Self-registered users : Auto activate and add ESS role ?

    Hi all ,
    we are allowing users to self-register for our ESS portal. We would like to auto-activate the users and give them the ESS role without any Admin action .
    Is this possible ?
    Regards
    Daniel

    Hello Daniel,
    please assign your ESS Role to the group "everyone".
    Then the self registered(but also every other user on the portal) will have this role by default.
    Assign Default Role to User
    Regards
    Frank

  • How to notify a self registered user that his/her request has been denied

    Hello,
    Is there a way to send an email to the requestor (this email address is what the user puts in the self registration form under requestor email) to notify that the request has been denied? (OIM 9.1)
    In The User Registration Process Definition, Task Awaiting Approval Data, I have the Assignment Tab set as follows:
    Rule: Default
    Target Type: Group
    Adapter AssignApproverGroup (this adapter dynamically looks for the members in a group based on the requestor organization, assigns the task to these individuals, and sends an email notifying that self registration approval is pending to all members of that approvergroup)
    Priority: 1
    Notification Tab
    Assignee is checked
    Status: R
    Email: Self registration request Denial
    When the Assignee logs in and denies the request, an email is sent to the Assignee about the denial.
    Questions:
    1. If the ApproverGroup has more than 1 member, how can we notify all the members of the Approver group that the request has been denied?
    2. How can we notify the requestor that his/her request has been denied using his/her provided email from the self registration form?
    Thanks
    Edited by: Khanh on Dec 4, 2008 3:36 PM

    You need to think about how the whole system is going to work - you need to know everything that the button will require, and then think about how to provide this information to the button.
    So, by the sounds of you need say a single button to press when you want to add a new button to the calculator. Associated with this have text fields that take the function for the calculator. I would specify that the function uses variables e.g. x and y as in function = x * y. Then your program could parse the input string describing the function, by recognising "*" to mean * in the Java code syntax and "/" to mean /. Then treat everything else as variables. Since you can filter out the other variables i.e. not the operators, you can then say associate an array to contain the values of these. Then when the user uses the button and specifies the input parameters and presses the button, you can update this array, and perform the calculation based upon these values.
    Hope this helps.
    My advice really is just to think about everything that a button that creates new function buttons is going to need.
    PS. Remember to repaint the GUI once update its Container. Swing does this automatically, but I always specify it explicitly anyway to be safe. You can use either repaint(), validate(), or revalidate().
    Goodluck mate!

  • Error on accessing the OIM Self Register page.

    Hi,
    I had modified the 'Self Register' Request template on the Admin Console UI to include a new custom attribute.
    Since then, I have removed the custom attribute from the User Configuration and uploaded a new SelfCreateUserDataset.xml.
    On accessing the self register page, it throws the an error with the following message: -
    "Invalid restriction specified for the attribute Role in template Self-Register User. Corresponding Attribute or Attribute Reference not found in the Request Data Set."
    Kindly let me know how to restore the template in UI to the factory setting.
    Thank you,
    Bhaskar

    -

  • Self-registration user assigned to anonymous group auto

    hi experts,
    how can i make the user self-registration user belong to anonymous group,not everyone group
    best regards
    zlf

    Normally self  registered users automatically assigned to everyone group. If client needs they should automatically assign to someother group , it is the only possibility in my point.
    Ulitimately when modifying standard groups, this consultant should think about it whether modification really needed ?
    It is just an idea
    Koti Reddy
    Edited by: Koti Reddy Chimalamarri on Feb 8, 2009 12:03 PM

  • Self registering of Guest user

    Hi,
       I want to enable the self register option for the guest user.I can't see self-registration link on the Welcome screen.I have done the following steps.
    1.Ticked self-registration for guest at UME.
    2.Seted ume.logon.selfreg=TRUE in VA.
    3.Assign the action "ume.selfregister_user" to the    role "Everyone"
    4.and finally restarted.
    but still I am unable to see the link for "Self Registering".
    Am I missing something?
    Regards
    Indranil

    Hi Indranil,
    You have missed the following two steps after server restart:
    1)  Configure the Standard User Role (eu_role):
    a. Navigate to Content Administration --> Portal Content
    b. Navigate to Portal Content --> Portal Users --> Standars Portal Users -->Standard User Role.
    c. Open the Standard User Role
    d. select in the "property Catagory" combo box in the property Editor frame  the "User Management  Permissions" option.
    e. Change the following fields:
    i. Manage_My_Profile --> yes
    ii. Manage_My_Password --> yes
    iii. Read_My_Profile -->yes
    iv. Selfregister_User --> yes
    f. Save the changes in the save button in the left size of the screen.
    And then,
    2)  Assign eu_role to everyone group
    - Anagha

  • OIM: Error while deploying Custom Approval Process for Self-Register

    While deploying the Custom Approval Process for Self-Register, i am getting the following error in scac.log file
    Nov 16, 2011 2:48:58 PM oracle.fabric.common.wsdl.SchemaManager isIncrementalBuildSupported
    INFO: XMLSchema incremental build enabled.
    Nov 16, 2011 2:48:58 PM com.collaxa.cube.CubeLogger info
    INFO: validating "ApprovalProcess.bpel" ...
    oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
         at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
         at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
         at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:155)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:271)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:153)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:51)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
         at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
         at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
         at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
         at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
         at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
         at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
         at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
         at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
         at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
         at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
    Nov 16, 2011 2:49:00 PM CubeProcessGenerator compile
    WARNING: classpath is: D:\JDev11g\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;D:\OIMPS1\Middleware\oracle_common\modules\oracle.jps_11.1.1\jps-manifest.jar;;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\gen-classes;D:\OIMPS1\Middleware\Oracle_IDM1\server\workflows\new-workflow\process-template\SelfRegistrationApprovalApp\SelfRegistrationApproval\SCA-INF\lib\oimclient.jar;D:\JDev11g\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;D:\JDev11g\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\user-patch.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;D:\JDev11g\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.workflow_11.1.1\bpm-services.jar;D:\JDev11g\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
    In scac_out.xml file following is the error message
    <Fault>
    <severity>error</severity>
    <loc>/ns:composite</loc>
    <line/>
    <col/>
    <file/>
    <msg>
    <![CDATA[SCAC-50012]]>
    </msg>
    </Fault>

    Hi,
    I have run into the same problem with SOA 11.1.1.5 version. In my case after fixing the following two errors it seems to work fine.
    If you have followed the guide, there must be some errors:
    First the java code if copied then contains an extra enter value:
    Instead of:
    "try {
    System.out.println("Prototype for invoking an OIM API from a SOA Composite");
    System.out.println("RTM Usecase: Self Registration Approval by Organization
    Administrator");"
    Use the following:
    "try {
    System.out.println("Prototype for invoking an OIM API from a SOA Composite");
    System.out.println("RTM Usecase: Self Registration Approval by Organization Administrator");"
    The other error is that you should not use <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-manifest.jar, but the <BEAHOME>/oracle_common/modules/oracle.jps_11.1.1/jps-api.jar in jdeveloper. After these the deployment to the application server works fine for me.

  • How to register User custom field using PHP?

    Hi!
    I am looking for a way to share user specific data between connected users. For example, all participants should know each other IDs(our own system IDs, not LCCS).
    User's custom fields looks the best solution for this, but I can't find a way to register one using PHP, while creating room.
    How to register User's  custom field using PHP? Or may be there are better solution to make such things?

    Got it, just need to add new node to UserManager collection.
    const USER_MANAGER_COLLECTION = 'UserManager';
    static private $USER_MANAGER_CUSTOM_FIELD_CONFIGURATION = array(
       'accessModel'=>self::ROLE_VIEWER,
       'publishModel'=>self::ROLE_VIEWER,
       'persistItems'=>true,
       'modifyAnyItem'=>false,
       'userDependentItems'=>true,
       'sessionDependentItems'=>false,
       'itemStorageScheme'=>self::STORAGE_SCHEME_MANUAL,
       'allowPrivateMessages'=>true,
       'lazySubscription'=>false,
       'p2pDataMessaging'=>false
    const USER_INVITE_ID_CUSTOM_FIELD = 'inviteId';
    static private function createUserManagerCustomFields($room){
       $account = self::init();
       $collection = self::USER_MANAGER_COLLECTION;
       $account->subscribeCollection($room, $collection);
       $account->createNode($room, $collection, self::USER_INVITE_ID_CUSTOM_FIELD, self::$USER_MANAGER_CUSTOM_FIELD_CONFIGURATION);

Maybe you are looking for