none
Export Precedence RRS feed

  • Question

  • In the Export Precedence section of About Attribute Flow Precedence, the reason for my Skipped: not precedent is clearly described. However, I am still at a loss as to how to make FIM do what I want. How might I set up FIM to accommodate the following situation?

    An HR system contributes employees to the metaverse, while contractors are manually entered into the FIM Portal. In the MV, the employeeType attribute needs to be populated. employeeType also needs to flow back to the FIM Portal for both contractors and employees, so MPRs/Sets/Workflows can be applied.

    The HR sync rule contributes "Employee", while the FIM Portal contributes "Contractor". The MV has to flow back to the FIM Portal to update employees. If HR is precedent, "Contractor" never flows to the MV. If the Portal is precedent, "Employee" flows from HR to the MV to the Portal at projection, but then the Portal becomes precedent and a hired contractor cannot be updated when HR joins later.

    It seems like there is no solution to this. I hope I am somehow misunderstanding. Any help would be appreciated.

    Thanks in advance.

    Saturday, November 16, 2013 12:22 AM

Answers

  • Hello,

    normally you would use manual precedence but this isn't possible on the FIM mA badly.

    So you will maybe have luck with equal precedence, but even this should be avoided as it is an deprecated feature and will be removed next version.

    I think best way will be to have seperate objectTypes for contractors and employees but let both flow to users object class in AD.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    • Marked as answer by PeteA Friday, November 22, 2013 2:27 PM
    Sunday, November 17, 2013 12:13 PM

All replies

  • Hello,

    normally you would use manual precedence but this isn't possible on the FIM mA badly.

    So you will maybe have luck with equal precedence, but even this should be avoided as it is an deprecated feature and will be removed next version.

    I think best way will be to have seperate objectTypes for contractors and employees but let both flow to users object class in AD.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    • Marked as answer by PeteA Friday, November 22, 2013 2:27 PM
    Sunday, November 17, 2013 12:13 PM
  • Hello,

    Maybe, you can  use two employeeType attributes in the MV:

    • employeeType
    • employeeTypeHR

    The Sync rule HR set employeeTypeHR to "employee" in the MV and you export this attribute to EmployeeType in the Portal (do not check "allow null" on the MA FIM)

    The Portal set employeeType with the EmployeeType value in the MV.

    So, with this, you will not have precedence issue

    Regards


    Sylvain

    Monday, November 18, 2013 4:49 PM
  • But remember "disable allow null" is also a deprecated feature and will maybe removed in next version, so you have to find another solution before upgrading.

    Regards
    Peter


    Peter Stapf - Doeres AG - My blog: JustIDM.wordpress.com

    Monday, November 18, 2013 4:56 PM