Can esignature information be exported outside of SDD? You can export the esignature of one or more objects in an SDD folder by selecting the objects and then selecting "Actions --> Export Esign". The exported file that is created is a zip file and contains a file for each version of each object along with a corresponding xml file that contains the signature information. The exported file can be saved within SDD or outside of SDD (on local client machine). When the exported file is saved outside of SDD, you can run a verifier program to verify that the signature corresponds to the file that was signed and that nothing was altered. A note about the archive function within SDD: If you archive a folder by selecting a folder and then selecting Archive, there is a separate file created for each versioned object. However the only information about the esignature is contained in the archived audit trail information. There is also information in the properties file for an object, but that only contains the information for the latest version of the object. The actual esignature is not contained in the archive. ... View more

What is the difference between active, inactive, and locked users in SDD 4.x? All accounts have a status of active or inactive.  An account can also be locked.  When an account is locked, the user is not able to log in and the account needs to be unlocked by an administrator.  An account is automatically locked if the user exceeds the number of allowable login attempts.  An administrator can also lock a user’s account by editing the user information under Administration --> Users.    When an account is locked, there are no changes made to the account.  However it is not accessible to the user until it is unlocked. A user is not able to log into an inactive account.  When an account is inactivated, the userid is removed from all groups which the userid was assigned to.   When the account is activated again by the administrator, the userid must be reassigned to the necessary groups.  It is possible for an administrator to manually activate and inactivate an account.  It is also possible for the adminstrator to set a date range for the account, such that the account is active on the "Start Date" and becomes inactive on the "Expiration Date".  ... View more

Batch Loading New Users SAS Drug Development provides a way to create multiple user accounts at one time through a batchload users facility. The user information for creating new accounts can be read from an XML file. Batch loading users requires the same user information as if you are creating a single new user account in SAS Drug Development. In addition to creating an account for each user, batch loading of users offers the following capabilities: Selecting specific users for upload from a batch list Adding additional user data (name, title, phone number, etc) for the loaded users Setting a default password for the users being loaded Adding the users to existing SAS Drug Development groups Setting default SAS Drug Development policies for the users being loaded Confirmation of selected information prior to final load procedure. The XML file used for batch loading of users must contain the same user information that would be entered as if you are creating a single new user account in SAS Drug Development. A sample XML file is below. <?xml version="1.0"encoding="UTF-8" ?>       <loadUsers>        <user>        <username>orgjod</username> <firstname>John</firstname>        <lastname>Doe</lastname>        <email>John.Doe1@org.com</email>         </user>         <user>         <username>orgjad</username> <firstname>Jane</firstname>         <lastname>Doey</lastname>         <email>Jane.Doey1@org.com</email>         </user>         </loadUsers> In order to load the XML file, go to Admin --> Users.  Select Loader --> XML.  You will then be prompted for the XML file. ... View more

The archive function within SDD creates separate files for each version of an object in the directory being archived. If you archive a directory, a jar file is created containing all of the files in that directory.  That jar file is written to the archives folder in the SDD instance. If there are any versioned files in the directory, they will appear in the archive with an extension of "SDDVerxofx". Here's an example: demo.sas7bdat_SDDVer1of2.sas7bdat demo.sas7bdat_SDDVer2of2.sas7bdat If saving the .jar file to a Windows machine, the extension will need to be renamed from .jar to .zip.    Prior versions of a files can also be retrieved using the Remote API. ... View more