App Permissions:
Description:
App permissions are the permissions which restrict the users to view or change at
Field Level, Dynamic View Level, Link Menu Level and X-Tab Level.
Note: Please find the below info
Root map for App Permissions Window
Login in to cBizOne as Admin
- Click on Edit à Select Users…
- Select the User account on which the App Permission has to be set
- Click on Modify
- Click on App. Permissions
- Write the App permission code in the App permissions window.
Example:
AppPermission for giving the access to dashboard:
<AppPermissions>
<AddEntities>
<AddEntity AddTo="cBizOne" ID="Dashboard"
Caption="Dashboard">
<AddTab Caption="TheDashboard"
URL="TheDashboard.htm" UserIDs=""/>
<AddTab Caption="GoogleMashupDash"
URL="GoogleMashupDash.htm" UserIDs=""/>
</AddEntity>
</AddEntities>
</AppPermissions>
Example:
Following are some of the examples of the App permissions
- To disable the options of selecting MS Access and SQL Server.
Screenshot before App permissions implementation:
<AppPermissions>
<frmOptions>
<optSQLServer>
<Enabled>False</Enabled>
</optSQLServer>
<optMSAccess>
<Enabled>False</Enabled>
</optMSAccess>
</frmOptions>
</AppPermissions>
Screenshot after App permissions implementation:
- To disable the options of selecting either opening the existing email account
or to create the new email account.
Screenshot before App permissions implementation:
<AppPermissions>
<frmEMail>
<cmdAccountOpen>
<Enabled>False</Enabled>
</cmdAccountOpen>
<cmdAccountNew>
<Enabled>False</Enabled>
</cmdAccountNew>
</frmEMail>
</AppPermissions>
Screenshot after App permissions implementation:
- To disable or make a Field or Tab invisible in the form, following
is the example:
- We are making the Home Phone field invisible, Mobile Phone field disable, Details
tab invisible and the Skills tab disable in the Candidate form.
- In the Requirement form we are making the Contact field invisible.
Screenshot before App permissions implementation:
Screenshot before App permissions implementation:
<AppPermissions>
<frmItem>
<Consultants>
<XFields>
<MobilePhone>
<Enabled>False</Enabled>
</MobilePhone>
<HomePhone>
<Visible>False</Visible>
</HomePhone>
<MainTab>
<TabVisible>2,False</TabVisible>
<TabEnabled>3,False</TabEnabled>
</MainTab>
</XFields>
</Consultants>
<Requirements>
<XFields>
<Contact>
<Visible>False</Visible>
</Contact>
</XFields>
</Requirements>
</frmItem>
</AppPermissions>
Screenshot after App permissions implementation:
- To hide the entire fields in the View following is the example:
Screenshot before App permissions implementation:
<AppPermissions>
<frmItems>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
</Views>
</Requirements>
</frmItems>
</AppPermissions>
Screenshot after App permissions implementation:
- To make only some columns visible in the list view following is the example:
- In the following view Display Name, Job Type, Location fields are made invisible.
Screenshot before App permissions implementation:
<AppPermissions>
<frmItems>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Contacts.CompanyName>
<Visible>True</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Categories>
<Visible>True</Visible>
</Categories>
</RecordsetFieldNames>
</Views>
</Requirements>
</frmItems>
</AppPermissions>
Screenshot after App permissions implementation:
- To make all the fields in the X-tabs invisible.
Screenshot before App permissions implementation:
<AppPermissions>
<frmItems>
<Requirements>
<XTabs>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
</XTabs>
</Requirements>
</frmItems>
</AppPermissions>
Screenshot after App permissions implementation:
- To make all the fields in the Document X-tabs invisible.
Screenshot before App permissions implementation:
<AppPermissions>
<frmItems>
<Requirements>
<XTabs>
<Documents>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
</Documents>
</XTabs>
</Requirements>
</frmItems>
</AppPermissions>
Screenshot after App permissions implementation:
- Following is the example which explains how to make some fields in the
X-tab invisible.
- The Contact, Candidate, Job Title fields are hidden in the X-tab.
Screenshot before App permissions implementation:
<AppPermissions>
<frmItems>
<Requirements>
<XTabs>
<ConsSent>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Consultants.DisplayName>
<Visible>True</Visible>
</Consultants.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Subject>
<Visible>True</Visible>
</Subject>
<Type>
<Visible>True</Visible>
</Type>
<SubType>
<Visible>True</Visible>
</SubType>
</RecordsetFieldNames>
</ConsSent>
</XTabs>
</Requirements>
</frmItems>
</AppPermissions>
Screenshot after App permissions implementation:
- The following example shows how to hide some fields in the
linking windows.
- The Job Type field was made invisible in the Linking windows
Screenshot before App permissions implementation:
<AppPermissions>
<frmLinkItems>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Contacts.CompanyName>
<Visible>True</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Requirements>
</frmLinkItems>
</AppPermissions>
Screenshot after App permissions implementation
:
Screenshot before App permissions implementation:
<AppPermissions>
<frmLinkItem>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Contacts.CompanyName>
<Visible>True</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Requirements>
</frmLinkItem>
</AppPermissions>
Screenshot after App permissions implementation:
A sample App Permission to hide contact details.
<AppPermissions>
<frmItem>
<Requirements>
<XFields>
<Contact>
<Visible>False</Visible>
</Contact>
</XFields>
</Requirements>
</frmItem>
<frmItems>
<Requirements>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<DisplayName>
<Visible>False</Visible>
</DisplayName>
</RecordsetFieldNames>
</Views>
<XTabs>
<ConsSent>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
</RecordsetFieldNames>
</ConsSent>
<ConsRecv>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
</RecordsetFieldNames>
</ConsRecv>
<ConsPot>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
</RecordsetFieldNames>
</ConsPot>
</XTabs>
</Requirements>
</frmItems>
<frmLinkItems>
<Requirements>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
</Views>
</Requirements>
<Consultants>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
</Views>
</Consultants>
</frmLinkItems>
<frmLinkItem>
<Requirements>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
</Views>
</Requirements>
<Consultants>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
</Views>
</Consultants>
</frmLinkItem>
</AppPermissions>
Note: Make the Contact Record Private.
A sample App Permission to hide Contact and
Company details.
<AppPermissions>
<frmItem>
<Requirements>
<XFields>
<Contact>
<Visible>False</Visible>
</Contact>
</XFields>
</Requirements>
</frmItem>
<frmItems>
<Requirements>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Company>
<Visible>False</Visible>
</Company>
<Contact>
<Visible>False</Visible>
</Contact>
<DisplayName>
<Visible>False</Visible>
</DisplayName>
<CompanyName>
<Visible>False</Visible>
</CompanyName>
</RecordsetFieldNames>
</Views>
<XTabs>
<ConsSent>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<Company>
<Visible>False</Visible>
</Company>
</RecordsetFieldNames>
</ConsSent>
<ConsRecv>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<Company>
<Visible>False</Visible>
</Company>
</RecordsetFieldNames>
</ConsRecv>
<ConsPot>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<Company>
<Visible>False</Visible>
</Company>
</RecordsetFieldNames>
</ConsPot>
</XTabs>
</Requirements>
<Consultants>
<XTabs>
<ConsSent>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<Company>
<Visible>False</Visible>
</Company>
</RecordsetFieldNames>
</ConsSent>
<ConsRecv>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<Company>
<Visible>False</Visible>
</Company>
</RecordsetFieldNames>
</ConsRecv>
<ConsPot>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
<Company>
<Visible>False</Visible>
</Company>
</RecordsetFieldNames>
</ConsPot>
</XTabs>
</Consultants>
<Companies>
<XTabs>
<Requirements>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
</RecordsetFieldNames>
</Requirements>
<ConsSent>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
</RecordsetFieldNames>
</ConsSent>
<ConsRecv>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Contact>
<Visible>False</Visible>
</Contact>
</RecordsetFieldNames>
</ConsRecv>
</XTabs>
</Companies>
</frmItems>
<frmLinkItems>
<Requirements>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Requirements>
<Consultants>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Consultants>
</frmLinkItems>
<frmLinkItem>
<Requirements>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Requirements>
<Consultants>
<Views>
<DatabaseFieldNames>
<Contacts.DisplayName>
<Visible>False</Visible>
</Contacts.DisplayName>
<Contacts.CompanyName>
<Visible>False</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Consultants>
</frmLinkItem>
</AppPermissions>
A sample App Permission code with above all Constraints.
<AppPermissions>
<frmOptions>
<optSQLServer>
<Enabled>False</Enabled>
</optSQLServer>
<optMSAccess>
<Enabled>False</Enabled>
</optMSAccess>
</frmOptions>
<frmEMail>
<cmdAccountOpen>
<Enabled>False</Enabled>
</cmdAccountOpen>
<cmdAccountNew>
<Enabled>False</Enabled>
</cmdAccountNew>
</frmEMail>
<frmItem>
<Consultants>
<XFields>
<MobilePhone>
<Enabled>False</Enabled>
</MobilePhone>
<HomePhone>
<Visible>False</Visible>
</HomePhone>
<MainTab>
<TabVisible>2,False</TabVisible>
<TabEnabled>3,False</TabEnabled>
</MainTab>
</XFields>
</Consultants>
<Requirements>
<XFields>
<Contact>
<Visible>False</Visible>
</Contact>
</XFields>
</Requirements>
</frmItem>
<frmItems>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Contacts.CompanyName>
<Visible>True</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Categories>
<Visible>True</Visible>
</Categories>
</RecordsetFieldNames>
</Views>
<XTabs>
<!-- This will hide ALL Fields in ALL Tabs.
<_AllFields>
<Visible>False</Visible>
</_AllFields>
-->
<ConsSent>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Consultants.DisplayName>
<Visible>True</Visible>
</Consultants.DisplayName>
</DatabaseFieldNames>
<RecordsetFieldNames>
<Subject>
<Visible>True</Visible>
</Subject>
<Type>
<Visible>True</Visible>
</Type>
<SubType>
<Visible>True</Visible>
</SubType>
</RecordsetFieldNames>
</ConsSent>
</XTabs>
</Requirements>
</frmItems>
<frmLinkItems>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Contacts.CompanyName>
<Visible>True</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Requirements>
</frmLinkItems>
<frmLinkItem>
<Requirements>
<Views>
<_AllFields>
<Visible>False</Visible>
</_AllFields>
<DatabaseFieldNames>
<ReqID>
<Visible>True</Visible>
</ReqID>
<JobTitle>
<Visible>True</Visible>
</JobTitle>
<Contacts.CompanyName>
<Visible>True</Visible>
</Contacts.CompanyName>
</DatabaseFieldNames>
</Views>
</Requirements>
</frmLinkItem>
</AppPermissions>
__________________________________________________________________________
App Permission code for Candidate Fetch Application to
Restrict Number of Resume download per day at recruiter level.
<AppPermissions>
<CustomCandidateFetch>
<ResumeRepository name="monster">
<DailyLimit>5</DailyLimit>
<ResumeDate>05/24/2011</ResumeDate>
<DownloadedSoFar>0</DownloadedSoFar>
</ResumeRepository>
<ResumeRepository name="Naukri">
<DailyLimit>5</DailyLimit>
<ResumeDate>05/24/2011</ResumeDate>
<DownloadedSoFar>0</DownloadedSoFar>
</ResumeRepository>
<ResumeRepository name="timesjobs">
<DailyLimit>3</DailyLimit>
<ResumeDate>05/24/2011</ResumeDate>
<DownloadedSoFar>3</DownloadedSoFar>
</ResumeRepository>
</CustomCandidateFetch>
</AppPermissions>
Note: You can adjust the Daily Limit accordingly.
