Assembly Editor
...
Editor functionality
Developer options
7 min
the developer menu contains options for people who build assemblies open admin console developer account who have the "admin console" permission will have this option to open the admin console in a new browser tab/window open appjsp javadoc the extension server side script module allows java jsp code to be inlined within assembly diagrams within the inlined java jsp code, the "appjsp" bean class (defined by default in the module's skeletal java jsp code) is used to access various functionality this option opens a link to javadoc documentation for the available methods open vtd xml parser javadoc the extension server side script module allows java jsp code to be inlined within assembly diagrams within the inlined java jsp code, the 3rd party vtd xml (virtual token descriptor) parser is used to work with xml this option opens a link to javadoc documentation for the available methods open your trace log each assembly developer account has their own trace log that can be written into via system out println() statements in java jsp code within extension server side script modules purge your trace log your account's trace log can be cleared with this option open system webhooks log this option will appear if the system is a development server (see development server docid\ ojdm8fxr if e8hqgjfky ) or if your account has the "admin console" permission opens the system's webhooks log, which contains webhooks recently received by the system by default, the log rolls over when it reached 10mb in size so it does not contain all webhooks ever received by the system empty system webhooks log this option will appear if the system is a development server (see development server docid\ ojdm8fxr if e8hqgjfky ) or if your account has the "admin console" permission empties the system's webhook log by performing a log rollover the logged data is not deleted on the server execute this assembly on the server opens a new browser tab/window and executes the current assembly on the server the assembly should first be saved the server executes the most recently saved version of the assembly request a review of this assembly this option will appear if the current account does not have the "assembly reviewer" permission the system supports a development cycle for assemblies where assembly developers can submit their work to accounts having the "assembly reviewer" permission, then receive feedback from the reviewers this link will open a dialog where the developer can first supply any comments to send to the reviewer upon clicking ok, the system will send a review request email to all active accounts having the "assembly reviewer" permission for more information, see assembly development cycle docid\ uix2pca zqeqfvwvpk2sq