Track versions of rulebase documents

Track versions of rulebase documents

Placing a rulebase project under source control allows you to track versions of the project documents, by checking files out before making changes, and then checking them back in again to commit those changes to the source-controlled project.

What do you want to do?

Check out a document from source control

Check in a document to source control

See whether a document is checked in or out

View the version history of a document 

Ensure all documents are checked in when the project is closed

See which documents have not been added to source control

Check out a document from source control

To check out a file:

  1. In Oracle Policy Modeling, right-click on the file name in the Project Explorer and select Check Out.
  2. Select the files to check out and, if required, add a comment.



  3. Click the Check Out button to check the file out.
  4. Log in to source control using Username and Password, then click OK.

You can undo the check out by right-clicking the file name in Project Explorer and clicking the Undo Check Out menu option in the pop-up menu.

NOTE: Attempting to edit checked-in screen (*.xint) and properties files (*.xsrc) will automatically prompt you to check out the file.

TIP: To check out a file for editing, select Check Out and Edit from the popup menu in step 1 above. This will check out the file and open it ready for editing (eg in Word, Excel, Oracle Policy Modeling).

Check in a document to source control

To check in a file:

  1. In Oracle Policy Modeling, right-click on the file name in the Project Explorer and select Check In.
  2. Select the files to check in and, if required, add a comment.



  3. If you want to update the master copy of the file while keeping the file checked out, select the Keep checked out check box.
  4. Click the Check In button to check the file in.

TIP: Files which cannot compile or build should be corrected before being checked into source control.

See whether a document is checked in or out

On shared projects, you may want to update the source control status of documents from time to time to see whether or not another team member is working on a project document.

A small blue padlock on a project file icon shows that a file is checked in.



A tick on a project file icon shows that a file is checked out.

View the version history of a document 

Each time you check in a file under source control, a version of that file is kept along with details of the changes made. If you are using Subversion for your project source control, you can view the history of all changes made to a document from within Oracle Policy Modeling. To do this:

  1. In Oracle Policy Modeling, right-click on the file name in the Project Explorer and select Version History.
  2. All changes made to the document are shown, including the date the change was made and any comments entered when the document was checked in.

 

You can also compare versions of Word rule documents and retrieve a specific version from the change history. If you are not using Subversion for your project source control, you can access the version history for the document directly from the source control program.

Ensure all documents are checked in when the project is closed

You can set a reminder for you to check in all of the files you have checked out whenever you close the project. To do this:

  1. In Oracle Policy Modeling, select Tools | Options | Environment | Source Control.
  2. Select the option When a project is closed remind me to check in all of the files I have checked out.

See which documents have not been added to source control

You can also set an option to see all of the files which have not been added to source control whenever you close a source-controlled project. To do this:

  1. In Oracle Policy Modeling, select Tools | Options | Environment | Source Control.
  2. Select the option When a project is closed show me all of the files that have not been added to source control.

 

See also: