1 Reply Latest reply on Jan 10, 2008 10:20 PM by Bill Robinson

    Change Control Scenario

      I'm looking for ideas around how to accomplish the following:


      When a user executes a job, check a change management system for approval. This needs to work for a deploy job and BLPackage that have just been created by this user, such that the user can create the BLPackage and the deploy job, but cannot execute it until the execution is approved.

        • 1. Re: Change Control Scenario
          Bill Robinson

          look at this:



          you might need to have 2 different roles for the user - that of 'packager' that can create the package and job, and the role of 'deployer' that can execute the job. and you'd really need a 3rd role that could 'promote' the package.


          if the role has job.create and job.execute, i think when they create the job, they will get execute rights as well - double check that though. if that's not the case, they'd create the package and job, then something would run to grant them job.execute on the job. (or whatever the right permission name is)


          the script in the kb article does some acl template applications based on a property value set on the package/job to set the permissions appropriately.