Dialog for checking in files to Perforce
Do not accept the default SECURITYRESOURCE from the superclass as this page handles it's own security to allow TrakCare use-cases
NOTE - this parameter is not enforced until 3012.2
This Parameter should be updated when synced from Perforce
Revision number of this class when compiled as part of the //custom_ccrs/_common/config/... branch. This version will not be updated (by design) when the class is integrated to other branches. This allows the user to tell what version of the Studio client tools are in use.
CSP Applications allowed to access this UI.
To add web applications to the return list, set
^%SYS("SourceControl","AllowedApps")=$lb(app1,app2,...). NOTE: app1, app2, etc must have a trailing '/', e.g.
Displays a diff between the file passes in the file url parameter and file_".bak" if it exists
Returns boolean value indicated whether or not the diff UI can be displayed
Set ^SYS("SourceControl","UIConfig","DisableDiff")=1 to disable diff for a specific namespace
Set ^%SYS("SourceControl","UIConfig","DisableDiff")=1 to disable diff for the entire instance
runs the DSCheckpointExport() method
Pages inheriting from %CSP.Page don't have a %GetParameter() method until 2010.2. This method allows access to the parameter values in the class from outside of the class
Returns value the Major.Minor version for this instance, so it can be used in comparison code which makes sure certain features are used in appropriate versions
If login needed (connected multi-developer instance), displays/processes the login form. Other UIs can call this and examine pLoggedIn to determine if processing should continue.
Event handler for PAGE event: this is invoked in order to generate the content of a csp page.
Ensure that this page is only accessible through approved CSP Applications
Returns true if the user has a valid Perforce ticket in the CSP session, otherwise returns false.
Also obtains and validate an existing ticket.
This also inializes the process ticket variable, so this must be called whenever a server-side method requiring Perforce access is invoked
Accepts the password for the current Perforce user (defined by $USERNAME) and validates password by attempting to log into Perforce and obtain a IP-bound ticket
If login is successful, ticket is stored in the session to be reused on later calls to Perforce
If Password is not defined, then the locally cached ticket will be cleared
Retrieve details of the requested CCR and update the UI with the details
Link to this page
Called from UI Bundle page to validate whether an ItemSet can be uploaded for a given CCR Updates elements on the page according to the status