• OverthinkerDave (Customer)

    Pro tip: Do not use account templates, unless you absolutely need to.

     

    Instead (as Boris said) you can use workflows for preparing attributes in a createAccount AFX operation.

     

    It is actually pretty simple (but very undocumented):

    • Set a workflow variable with the EXACT hard coded prefix "AFXCUSTOM_"
      • Example: "AFXCUSTOM_AD_HRSTART"
    • Then in AFX-connector call the value EXACTLY with the same hard coded prefix, but with following transform:
      • Remove the hard coded prefix "AFXCUSTOM_" above
      • Replace any left "_" with a "."
      • Change the character "case" to
        • first character "uppercase"
        • rest of charecters "lowercase"
      • Example: "AFXCUSTOM_AD_HRSTART" -> from workflow is called by this in connector mapping-> ${Ad.Hrstart}

     

    Although I do not know how these "workflow variables" affects database size and what "purging policy" is recommended.

    If you look under "Requests"->"Configuration"->"Workflow variables" then that page (for us) is full of "variables ready for purge".

    But I have no clue if it is safe to remove them, because there is the option "retain". And how long that retain is kept -> Unknown.

     

     

    Also don't forget that you can call attributes in connector directly from PV_USERS table by simply using connector mapping to the reserved word "User" -> Example: ${User.First_Name}

    In other words: For 1-to-1 attribute data (no transforms) you do not have to specify that attribut in a account template (and taking up space for neither "workflow variables" and/or "account template ids")

    Expand Post

    • Boris.Lekumovich (RSA)

      I don't quite see how you can avoid using an account template.

      without an account template the system will not create a change item for account creation.

      • OverthinkerDave (Customer)

        True: An account Template must always be used.

        The wording I should have used is: Only include mandatory attributes that can't be collected from PV_USERS view.

         

        For example I usually only configure to send the unique identifier that will link the account. Then (usually) the target system decides which unique account id I will get (which I catch in my AFX output parameter).

         

        The rest of the attributes needed (like firstname/lastname for friendlieness) is sent by calling ${User.First_Name} and ${User.Last_Name} in mapping for AFX create account. Plus that I can add all other "custom attributes" which the account template can't handle the transforms for.

         

        It has been some years now, but I have long time ago in this forum explained what need to be improved in the account template logic in this product, but nothing has since then been improved. We customers are stuck with this strange (limited and unstable) account creation process.

        Expand Post

Don't see what you're looking for?