Self Service Procurement

Get Involved. Join the Conversation.

Topic

    s k
    Requisition Approvals based on Information TemplateAnswered
    Topic posted November 13, 2019 by s kSilver Medal: 2,000+ Points, tagged Approvals, Requisition Processing 
    33 Views, 8 Comments
    Title:
    Requisition Approvals based on Information Template
    Summary:
    Requisition Approvals based on Context specific Information template fields
    Content:

    Hi,

    We have long information templates ( 10 to 15 fields ) based on context.

    Is it possible to use these fields to route requisitions for approval.

    Has anyone tried it.

    Please share your experience.

    Thank you

    Version:
    R13 19D

    Best Comment

    John Lay

    SK,

    If you were to use the Information Template DFF with Context defined you should be able to accomplish the goal. Each context group is the related Attribute List in the Information Template that becomes Smart Form specific. The AMX application for requisition approval includes the ability to apply line attribute 'Smart Form' to your rule condition and then add the DFF line attribute defined for 'High Security' to the condition and select Smart Form specific actions. Note that the Smart Form attribute when used requires an explicit 'is not blank' rule and may need a corresponding 'is blank' rule for other requisitions that may not use a smart form..

     

    Comment

     

    • Ashok

      S K

      As you must be aware the DFF infrastructure is available for approvals routing when you use BPM as your approvals configuration engine. Information Templates are also DFFs but I don't believe we support routing based on this. While I check to reconfirm, I am interested to understand what your use cases are. Can you share some examples on how you might author approval rules based on values provided in the Information Templates?

    • s k

      Hi Ashok,

      Please check with your team and confirm, if approvals can be routed based on information templates.

      There are many complex use cases we have.

      One of the simple one i can give is,

      For smart form A, we have a information template field, called High Security.

      If this field is checked, then we have to route the requisition for approval to Security team.

      We do not want to use a DFF, as this field is relevant for only smart form A.

      All other requisitions do not need this field.

      So for any fields which are specific to smart forms or purchasing categories, routing approvals based on information templates will help.

      I will look forward for your confirmation on this.

      Thank you

      • s k

        Hi Sumana,

        As you are the expert on Approvals.

        I want to know your views on approvals based on information template fields.

        I like John Lay's solution below with the smart form.

        However, i want you to confirm, if there is a way to create approvals rules based only on information template fields with context.

        Thank you

        • Sumana Sarkar

          Hello SK,

          Information template related contexts are not available for writing approval rules. Being so I would go with John Lay's approach.

          Thanks and Regards

          Sumana

    • Ashok

      SK

      As I inferred earlier, I also wanted to confirm with the approvals experts. We don't support Approval Rules on Information Template data. Do create an Idea in the Ideas Lab.

    • John Lay

      SK,

      If you were to use the Information Template DFF with Context defined you should be able to accomplish the goal. Each context group is the related Attribute List in the Information Template that becomes Smart Form specific. The AMX application for requisition approval includes the ability to apply line attribute 'Smart Form' to your rule condition and then add the DFF line attribute defined for 'High Security' to the condition and select Smart Form specific actions. Note that the Smart Form attribute when used requires an explicit 'is not blank' rule and may need a corresponding 'is blank' rule for other requisitions that may not use a smart form..

       

    • s k

      Hi John,

      Thank you for the insight.

      This is helpful and it will solve some requirements.

      We also have a requirement, where we are using an information template field not only on smart forms but on all requisitions.

      Is there a way to deal with such use cases without resorting to requisition DFFs.

      Thank you

       

       

    • John Lay

      If the field is applicable to all requisitions then it should be defined as a requisition DFF rather than Smart Form. Only decision is what level....header, line, distribution.