0 Replies Latest reply: Mar 7, 2014 2:07 PM by user8465477 RSS

    Auto-populate of SHELL_shellName_shell Upper form DE only functions in one single-instance project shell.  The DE in the BP Upper Form needs to auto-populate in two separate single-instance shells.  How can I get this DE to autopopulate in both?


        The Unifier environment
      contains two single-instance project shells, INF and PBS, and two multiple-instance child project shells, INFS and
      PB.    There is a single instance, non-workflow
      business process, ‘Project Information’ that contains a data element in the
      upper form definition, Project ID.  The Project ID is set to auto-populate from the multi-instance “INFS”
      project shell attribute, which is populated manually. 


      Issue:  The auto-populate functionality for the
      Project ID ‘Shell_shellName_shell’ data element within the single-instance
      Project Information BP only functions within one of the shells, either
      INFS or PB, but not both.  The INF and INFS shells are currently deployed
      to production, PB and PBS shell are not.



      It is critical that Project ID ‘Shell_shellname_shell’ data element is populated correctly in the
      Project Information upper form of both shells, INFS and PB,
      because that data element is referenced by multiple business processes and



      The attribute form definitions for both single and multiple instance project shells are identical.  The Project ID utilizes the same data
      element ‘SHELL_shellName_shell’ as is defined in both shell attribute forms
      (INFS and PB). 

      The data definition source is a Unifier system-level variable, SYS Shell
      Name (String, 128, Text Box)


      Potential Solutions:


      1. Create a Project ID DE of another data type which can
      be successfully auto-populated from either shell.  Drawback: all BPs and integrations which
      reference Shell_Shellname_shell will need to be rewritten.


      2. Investigate converting the Project Information single-instance
      to a  multi-instance BP, and create a
      separate instance for each single-instance shell type.  Same Drawback as Option #1, but with additional
      rework.  Most likely Project Information
      would have to be recreated as a new BP.
      Not sure that this option would even work.


      3. Create a separate Project Information BP for PB.  Drawback:  Two separate BPs for Project Information would
      need to be created.  All existing BPs
      refer to Project Information, so this option could potentially invalidate the
      ability to use the existing BPs in the PB shell.