1/ Validation Entries


Create an entry as below in the Validation Entries to specify the contract types that are below the level N (highest level)

the value in Text 1 depends on your own project structure, in the example below 3 Contract Types are below Project, which is the N level:




Then in the back end need to insert one entry per contract type including the level N:

For our example of 4 levels it is:


insert into tblValidationEntries (fkidBusinessUnit,cdValidCode,sgDisplay,sgValue)

values (0,'CONTRACTYP','PROJECT','PROJECT')


insert into tblValidationEntries (fkidBusinessUnit,cdValidCode,sgDisplay,sgValue)

values (0,'CONTRACTYP','STAGE','STAGE')


insert into tblValidationEntries (fkidBusinessUnit,cdValidCode,sgDisplay,sgValue)

values (0,'CONTRACTYP','SITE','SITE')


insert into tblValidationEntries (fkidBusinessUnit,cdValidCode,sgDisplay,sgValue)

values (0,'CONTRACTYP','LOT','LOT')


The structure of the Project is now created.


2/ Security Roles


We need now to add some new permissions to the existing security roles to allow the users to create Project job and/or view jobs in the Project structure.


Three new operation code/permissions: 

- Add Project (tick box Is project in the prompt New Contract when adding new job)

- Project Over View (main pane)

- Can View Project (Project node in the navigation tree)


The new permission Add Project should be added to the Security Roles that have the permission to add contract, with the same relationship (Contract Admin...)


The two permissions to view the Project should be added at minimum to the Security Role Basic Office User, with the same relationship.



The users need to log out and log back in to see the changes applied.