Workflow monitor agent controls

The Action Interval parameter of Workflow Monitor Agent is always controls, how the Action should be executed.
 
1) Just Navigate to Sitemap-> Administration->Server Configuration->Enterprises->Component Definitions->Choose Workflow Monitor Agent Component.

In the Component Parameters List choose Action Interval and check the default value is “3600” seconds (This is the default value to Action Interval Parameter).
 
2) Change the default value to 60. It means depending on the value of the Action Interval parameter for Workflow Monitor Agent, the action is taken.
3) Once Workflow Monitor Agent performs an action on the record in violation, an entry is logged into the S_ESCL_LOG table. If the same record comes into violation         again within the Action Interval time, the Workflow Monitor Agent will not perform the action again on the same record. It will only remove the row from S_ESCL_REQ table. As a result, it is possible that Workflow Monitor Agent clears many records from the S_ESCL_REQ table for which no actions have been performed.
4) Setting the Action Interval = 0 is not recommended by Siebel Systems because the following behaviors have been observed to occur with this setting:
->         Actions performed for rows in S_ESCL_REQ without checking if conditions are met or not.
->         Actions do not get executed at all at times.
->         Duplicate actions occur for the same record.
->         Performance issues occurs because this setting causes Workflow Monitor Agent to be busy all the time. Thus, Workflow can cause resource crunch in terms of CPU utilization and memory, etc.

Read Only Property, Applet Visibility Type property and Site Map

The Read Only property must be set to FALSE to use the Runtime property
to access multi-value groups and pick applets.

When the Applet Visibility Type property of the View Web Template Item
object is set to a non-null value, it might cause search specifications on the applets
in that view to be ignored.

Unlocking the Projects on Local from Backend

ometimes developers find the difficulty that when they GET all the projects from the server, some other user locked some of the projects. So the user cannot Lock these projects locally. Here is a few queries by which Projects can be unlocked locally from the Backend

Restrict the Entry of Characters in a List Column or Control

The length of the fields can be restricted on the application UI level with the help of the Field User Property called Text Length Override. Below is the syntax for configuring this Field User Prop:

Name: Text Length Override
Value:
For example, if the requirement is to restrict the 'Description' field in the 'My Opportunities View' to 10 characters, then perform the following steps:

How Can You Add Hidden Fields to a List Applet for Browser Script Access?

Background
 
A common business requirement is to have access to business component fields using browser script, but ensuring that these fields are not visible by the end users.  In Siebel 7, only fields existing on the UI are available to the GetFieldValue and SetFieldValue business component methods in browser script, regardless of the Force Active property value set for those fields.