User Guide > Studio Resource Management Overview > Getting Information about a Resource
 
Getting Information about a Resource
You can get information about a resource like who owns it, who created it, and when it was created as well as any annotations about the resource that might have been added.
The data source tabs display the following information about the resource.
Field
Description
Name
User-provided name and location.
Type
Resource type.
Owner
Name of the owner.
Orig Creation Date
Date the resource was created. If created in a release prior to TDV 6.2, this field contains Not Recorded.
Orig Owner
Name of the owner who created this resource. If created in a release prior to TDV 6.2, this field contains Not Recorded.
Last Modified Date
Date when the resource was last edited.
Last Modified User
Name of the user who last edited the resource.
Lock
Owner of the lock on the resource; or Not Locked.
Annotation
User-editable notes about the procedure.
Maximum Number In Queue
(All triggers except JMS triggers; in the Queue Properties section) Displays and lets you set the number of times a trigger can be queued simultaneously before duplicates are dropped.
A value of 1 (default) means that the queue for this trigger can contain only the trigger currently being processed. If the trigger repeats before the previous one finishes its task, it is lost.
When the value is set to 2 or greater, additional triggers start execution as soon as the current trigger finishes. Each refresh failure results in an email notification. A larger number of queues for a trigger reduces event loss but might use more memory.
(JMS triggers; in the Queue Properties section) TDV sets this field to 0. You cannot change it, because no message queueing is done inside TDV.
Target Definition Set
(XQuery transforms) The path to the definition set containing the schema.
Target Schema
(XQuery transforms) The fully qualified name space for the schema.
Execute only once per transaction for each unique set of input values
(XQuery procedures) If other procedures are called multiple times with the same parameter and values from within a procedure, it is invoked only once and the original results are reused. This ensures that the execution results of a procedure are kept intact for the transaction, as long as the procedure’s input parameter values remain the same. For details, see Setting Transaction Options for a Procedure.
To get information about a resource
1. Open the resource.
2. Select the Info or Configuration tab at the bottom of the resource editor.