View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

ERP/3.0/Developers Guide/Database Model/org.openbravo.model.ad.alert/AD AlertRule

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to ERP/3.0/Developers Guide/Database Model/org.openbravo.model.ad.alert


Contents

AD_AlertRule

This table contains the following columns:

Name Nullable Data Type Description


AD_AlertRule_ID No VARCHAR (32) Definition of the alert element.
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
AD_Org_ID No VARCHAR (32) An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
IsActive No CHAR (1) There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reporting. There are two reasons for de-activating and not deleting records:

(1) The system requires the record for auditing purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are existing invoices for it. By de-activating the Business Partner you prevent it from being used in future transactions.

Created No TIMESTAMP (7) The Created field indicates the date that this record was created.
Createdby No VARCHAR (32) The Created By field indicates the user who created this record.
Updated No TIMESTAMP (7) The Updated field indicates the date that this record was updated.
Updatedby No VARCHAR (32) The Updated By field indicates the user who updated this record.
Name No NVARCHAR (60) A more descriptive identifier (that does need to be unique) of a record/document that is used as a default search option along with the search key (that is unique and mostly shorter). It is up to 60 characters in length.
Sql Yes NVARCHAR (2000) SQL clause to be executed
FilterClause Yes NVARCHAR (2000) Filter clause
AD_Tab_ID Yes VARCHAR (32) The Tab indicates a tab that displays within a window.
Type No VARCHAR (60) The Type indicates the type of validation that will occur. This can be SQL, Java Script or Java Language.

Columns

Alert Rule



top


Client


Foreign key column to AD_Client table, (column: AD_Client_ID) It has a validation "AD_Client Security validation", with the following code

AD_Client.AD_Client_ID in (@#User_Client@)

top


Organization


Foreign key column to AD_Org table, (column: AD_Org_ID)

top


Active



top


Creation Date



top


Created By


Foreign key column to AD_User table, (column: AD_User_ID)

top


Updated



top


Updated By


Foreign key column to AD_User table, (column: AD_User_ID)

top


Name


top


Sql



Callout: SL_AlertRule_SQL

This column has a callout associated.

It is implemented by [1] Java Class.

top


Filter Clause



top


Tab


Foreign key column to AD_Tab table, (column: AD_Tab_ID)

top


Type



List values: AD_AlertRule Type

The allowed values for this list are:

top


Other Info

Back button.png   Back to org.openbravo.model.ad.alert

Retrieved from "http://wiki.openbravo.com/wiki/ERP/3.0/Developers_Guide/Database_Model/org.openbravo.model.ad.alert/AD_AlertRule"

This page has been accessed 1,000 times. This page was last modified on 18 November 2014, at 19:23. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.