cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sewechad
Level 4

License Policy Enhancement for Conditional Approvals using Criteria from Inventory Details Usage

Jump to solution
Currently, the License Policy only provides simplistic capability to approve or reject a license. We would like to add the capability to “Approve with Conditions” with the ability to define rule based criteria for when the license usage would be approved. The License Policy conditional rules would be aligned with the Inventory Details Usage questions that were introduced in 2019 R1. This feature would allow our legal team to create more fine grain licensing rules and spend less time reviewing project request that could be handled by conditional approvals rules. Example Conditionally Approved Rules: 1) MPL license would be approved if the open source code was “Not Modified” 2) EPL license would be approved if the following conditions were met: a) Open source code was “Not Modified” b) Component was “Dynamically Linked”
(1) Solution
sgeary
Revenera
Revenera

Hi sewechad,

We are planning on this sort of capability within our 2020R1 release where you will be able to include the usage type fields in policy decision.

Sean

View solution in original post

(1) Reply
sgeary
Revenera
Revenera

Hi sewechad,

We are planning on this sort of capability within our 2020R1 release where you will be able to include the usage type fields in policy decision.

Sean