Contract (ast_contract) who creates?; who approves?

[aaron47]

I was looking at the OOTB instance of Rome and I was struggling to see how it is meant to operate with contracts?

I believe only those with the contract_manager role is allowed to approve a contract - is that correct?

But for creating a contract, it appeared that anyone was allowed to create a contract.  This doesn't seem to make sense but from the ACL's I checked that's how it appears.

I was struggling to find a good article explaining how the contract lifecycle works (and who is responsible for what).

[Community Alums · Accepted solution]

Hi @aaron@parksvic ,

contract_manager role is the allowed to approve a contract !!

In a Layman language a guy with role can see the module, create a new contract, select an approver, save it then submit for review.

A new contract should have State = Draft, Substate = Awaiting Review

Once (UI Action) Submit for Review is clicked, State should not change, Substate = Under Review, and the only contract workflow should start. If new contract, workflow will follow below:

Once approved, the state of the contract is changed to either approved or rejected based on the End Date selected. Substate should be noce.

While the business rule - Manage Contract Lifecycle - is driving the state changes, the BR is getting what data to set from the Condition Check Definitions (module). Out of box choices look like this:

There is also a Scheduled job that runs daily named - Contract: Run Condition Checks - that checks the contract data against this table and moves the State/Substate based on the conditions defined in this table.

So a) confirm your workflow is running, b) confirm the condition checks table is populated correctly.

Refer to this.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep