You can change the values in effective dating fields in any view that contains the fields for an effective dating business component. The preconfigured Siebel.
Table of contents
Siebel 8.2.2 Case Management for Public Sector
For party-based business components, use a history table name that is consistent with the extension table name for the party-based business component. The following table includes the values in the columns for the column names in the history table. The following table includes the values in the columns for the additional column names in the table for the base business component.
After you create and update the tables for effective dating fields, you create a history business component for the history table, and you update the base business component. To create and update the business components for effective dating fields.
In this example, the name of the history business component is Account History. The following table includes the field and column names for the history business component. The following table includes the values in the columns for the field names in the base business component. In this example, the base business component is Account.
In this example, the base business component is Account, and the name of the history business component is Account History. Only agents with the proper authority can change the Status field value to Cancelled or Approved.
- Account Options.
- speed dating near farnborough.
- ?
- houston dating free.
Administrators set up this authority when they implement effective date tracking. For more information about setting up this authority, see Implementing Effective Date Tracking. Before changing a Status field value, an agent with the proper authority verifies the entry.
Siebel Public Sector Blackbook - Google Книги
This verification might involve reviewing supporting documentation for the entry or contacting people to check the validity of the entry. After verifying the entry, the agent performs the procedure in this topic to complete the verification. The Inactive field is selected for the inactive records and not selected for active records. After you close the dialog box when you approve the entry for a record, an attempt is made to adjust the date range of the prior approved entry so that this date range does not overlap the date range of the new approved entry.
If this attempt fails, then the Conflicting Approval Records dialog box appears showing prior approved entries with date ranges that overlap the date range of the new approved entry. For example, if a citizen's income affects the benefits determination, and if an agent learns of a change in the citizen's income two months after the change is effective, then the agent can enter the new income value in Siebel Public Sector and date that value two months earlier.
Consequently, the effective date of the income change, and not the date that the agent changes the income in Siebel Public Sector, is used to redetermine benefits for the citizen.
If you do no enable effective dating, then no functionality is available when users click the Link History button in a view.