www.usoft.com To www.usoft.com

Topics started by MaxMallon

21 Topics

MaxMallon
MaxMallon
published in XML internal component

XML.Query

This article is about the Query method of the XML internal component.XML.QueryExecutes a query that is defined in an input XML document. The structure of this XML document must comply with the Query By Form (QBF) specification described in XML Representation of Queries.Returns XML output that contains the query results. The structure of this XML output is described here. This XML output contains ALL column values of the records exported.SyntaxINVOKE XML.Query WITHSELECT header-line-name DTDName, use-io-formats UseIOFormats, document XMLDocumentFROM tableuse-io-formats := { No | Yes }where document is the only required output column.The optional header-line-name specifies a header line in the XML output with a DOCTYPE declaration containing this DTD Name as reference.The optional use-io-formats determines whether the column values in the resulting XML document must be formatted according to the IO Format of the corresponding domain or

521
R
6 months ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Tables

This article is about the Tables method of the USMeta internal component.USMeta.TablesAt runtime, gets metadata information about tables from the model developed in USoft Definer. This includes Database Tables, Logical Views, and Component Tables. For each retrieved table, this information takes the form of name/value pairs:Name Value TABLE_NAME Table Name MODULE_NAME If the table is not from a consumed module: the current application name. If you are calling from a USoft application, this is the USoft application name, eg., USD for USoft Definer. If you are calling from a User Application, this is the User Application name, eg. SALES. If the table is from a consumed module: the name of the consumed module. USABLE_AS_INTERFACE If the table is from a module loaded by the current application (either directly or indirectly via an intermediate module): the value of the Interface attribute (Y or N) as registered for the table in the module .CON file. Otherwise, '

1051
Harm Hofstee
8 months ago
MaxMallon
MaxMallon
published in XML internal component

XML.SQLStatementExport

This article is about the SQLStatementExport method of the XML internal component.XML.SQLStatementExportExports data to the Meta-Rows-Fields document format on the basis of a SELECT statement.This export method is the same as XML.SQLExport, except that the entire SELECT statement is passed as a variable element, which allows you to build or store a SELECT statement dynamically and then pass it to the export command.In the same way as XML.SQLExport, this export method has the drawback that the result is NOT re-importable with XML.Import.In the same way as XML.SQLExport, this export method has the advantage that it can deal with compound column expressions provided they are aliased. Also, the result contains metadata information. In summary, the result contains data but also information about how this data was queried.SyntaxINVOKE XML.SqlStatementExport WITHSELECT sql-statementsql-statement ::= SELECT value parameter-name , ... , expression alias

220
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.SQLExport

This article is about the SQLExport method of the XML internal component.XML.SQLExportExports data to the Meta-Rows-Fields document format on the basis of a SELECT statement.This export method has the drawback that the result is NOT re-importable with XML.Import.This export method has the advantage that it can deal with compound column expressions provided they are aliased. Also, the result contains metadata information. In summary, the result contains data but also information about how this data was queried.SyntaxINVOKE XML.SQLExport WITHSELECT value parameter-name, ..., expression alias, ...FROM ...WHERE ...GROUP BY ...ORDER BY …In the SELECT output list, value  parameter-name pairs and expressions may appear in any order. For possible parameter-names see the Parameters section later in this help topic.Example 1INVOKE XML.SQLExport WITHSELECT 'yes' UseIOFormats, *FROM tourExample 2The result of this c

570
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.SQL2XML

This article is about the SQL2XML method of the XML internal component.XML.SQL2XML Conversion table Description of result XML by element AssignmentList Column ConnectBy Delete Function GroupByList GroupByListElement Host Insert Invoke Method LogicalOperator Lowerbound MathOperator Operator OrderByList OrderByListElement Records RelateList RelateListElement RelateListElementTable Select SelectList SelectListElement SequenceColumn Set SetSelect SqlNode StartWith TableList TableListElement Top TopValue Update Where XML.SQL2XMLConverts SQL syntax to XML format. The SQL statement must be syntactically and semantically correct. If the SQL statement cannot be parsed, for example if tables or columns used in the SQL statement are not defined, an error is given.SyntaxINVOKE XML.SQL2XML WITH SELECT sql-statement SQLStatement, schema-path SchemaPath, xml-declaration XmlDeclarationFROM ...xml-declaration ::= { Yes |

560
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.MultiExportTables

This article is about the MultiExportTables method of the XML internal component.See also the Data flow control with XML or JSON section.XML.MultiExportTables Parameters AppendToFile ConvertWhiteSpaces EmptyDocOnZeroRows LOBAsCData ProcessingInstruction RestrictiveSupertypeListing WriteOutputTo XmlDeclaration Appended WHERE clauses Substitution variables in appended WHERE Behaviour with subtypesXML.MultiExportTablesExports data to the USoft XML multi-table format on the basis of a regular expression identifying a set of tables.Exports binary data (of the BLOB data type) to base64 encoding.Subtype indicators are not exported. See also the RestrictiveSupertypeListing parameter in this help topic.Using this method, you can create an output file with data from multiple tables. You can use XML.Import to re-import this result set into a target repository where each of the tables is present.SyntaxINVOKE XML.MultiExportTables WITH SELECTregular-expression, parameter, value, ...

3240
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.Import

This article is about the Import method of the XML internal component.See also the Data flow control with XML or JSON section.XML.ImportImports data presented in the USoft XML single-table format or the USoft XML multi-table format.Imports base64-encoded binary data (of the BLOB data type).IgnoreGUK parameter has been added.Processes the row elements found in the XML document one-by-one in document order. The default behaviour is "UPSERT" handling:A record is INSERTed if no record with the same primary key is found in the target table. No action is taken if a record with the same primary key, and no different values in other columns, is found in the target table. A record is UPDATEd if a record with the same primary key, but different values in other columns, is found in the target table. No record is DELETEd.This “UPSERT” handling may be modified by the usoft-xml processing instruction supplied at the top of the import document, by DML instruction tags supplied inside the row elements

3270
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.GenerateComplexType

This article is about the GenerateComplexType method of the XML internal component.XML.GenerateComplexTypeGenerates an XML complex type for an output XML Schema document.SyntaxINVOKE XML.GenerateComplexTypeWITHSELECT expression, ...FROM table ExampleINVOKE xml.GenerateComplexTypeWITHSELECT destination, descriptionFROM tourThis results in the following output:<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:USoft:Tours" xmlns:tns="urn:USoft:Tours"><xsd:complexType name="ToursEx"> <xsd:sequence> <xsd:element name="Tours" type="tns:Tours"></xsd:element> </xsd:sequence></xsd:complexType><xsd:complexType name="Tours"> <xsd:sequence> <xsd:element minOccurs="0" maxOccurs="unbounded" name="TOUR" type="tns:TOUR"></xsd:element> </xsd:sequence> <xsd:attribute name="documentName" type="xsd:string"></xsd:attribute></xsd:complexType>&lt

150
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.Export

This article is about the Export method of the XML internal component.See also the Data flow control with XML or JSON section.XML.Export Parameters AppendToFile ConvertWhiteSpaces DTDName EmptyDocOnZeroRows ExecutionType LeadingZeroForDecimal LobAsCData PrettyPrint TrimSpaces UseIOFormats WriteOutputTo XmlDeclaration XML.ExportExports data to the USoft XML single-table format on the basis of a SELECT statement.Exports binary data (of the BLOB data type) to base64 encoding.SyntaxINVOKE XML.Export WITHSELECT { parameter-assignment | column-expression } ...FROM tableORDER BY order-by-listparameter-assignment ::= value parametercolumn-expression ::= { column | OLD( column ) | * | OLD( * ) }The required SELECT clause must contain at least 1 item. Each item in this clause is either a parameter-assignment or a column-expression.Each parameter-assignment is a value-name pair. The SECOND element is the name of a para

3510
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in XML internal component

XML.CreateDTD

This article is about the CreateDTD method of the XML internal component.XML.CreateDTDGenerates DTD output based on a SELECT statement. The content of the DTD document is directly deduced from the table definitions in the repository.The resulting DTD output is a string. Only one document is generated, even if the SELECT retrieves more than one record. The structure of the DTD output is described in "Document Type Definition (DTD) Specification".This XML Create DTD method can for example be used in a corrective constraint, to fill or update a database column with the result of the DTD output.SyntaxINVOKE XML.CreateDTD WITHSELECT expression, expression...FROM tableexpression ::= { column | OLD( column ) | * | OLD( * ) }Only the selected columns are generated in the DTD output.The FROM clause may only contains a single table or logical view.Example 1Here is an example of a simple DTD creation:INVOKE XML.CreateDTD WITHSELECT

280
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Sets

This article is about the Sets method of the USMeta internal component.USMeta.SetsAt runtime, gets metadata information about sets from the model developed in USoft Definer. For each retrieved set, this information takes the form of name/value pairs. Each name/value pair expresses an attribute setting for the set. Information about set elements is also included.Returns an XML document of the form demonstrated in the Example below.SyntaxSELECT USMeta.Sets(    set-name-pattern Sets,   interfaces-only InterfacesOnly,   module-pattern Module,   mime-type MimeType)interfaces-only ::= { yes | no }mime-type ::= { application/xml , xml , application/json , json }All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The '.*application.*' value in the following example is for set-name-pattern because of the "Sets" alias:SELECT USMeta.Sets

70
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Roles

This article is about the Roles method of the USMeta internal component.USMeta.RolesAt runtime, gets metadata information about roles from the model developed in USoft Definer. For each retrieved role, this information takes the form of name/value pairs. Each name/value pair expresses a role attribute setting.Returns an XML document of the form demonstrated in Example 1 below.SyntaxSELECT USMeta.Roles(    role-name-pattern Roles,   description-pattern Description,   mime-type MimeType)mime-type ::= { application/xml , xml , application/json , json }All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The 'ADMIN' value in the following example is for role-name-pattern because of the "Roles" alias:SELECT USMeta.Roles( 'ADMIN' Roles )For backward compatibility only, it is possible to supply parameter values by position. Using this syntax, a list of non-aliased valu

210
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Relationships

This article is about the Relationships method of the USMeta internal component.USMeta.RelationshipsAt runtime, gets metadata information about relationships and relationship columns from the model developed in USoft Definer. For each retrieved relationship, this information takes the form of name/value pairs:Name Value PARENT_TABLE Parent Object CHILD_TABLE Child Object MODULE_NAME If the relationship is not from a consumed module: the current application name. If you are calling from a USoft application, this is the USoft application name, eg., USD for USoft Definer. If you are calling from a User Application, this is the User Application name, eg. SALES. If the relationship is from a consumed module: the name of the consumed module. The relationship is from a consumed module if it is in the .CON file that that module provides. If the parent table and child table are both usable as interface, it is also possible for the current application to define the rel

120
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Modules

This article is about the Modules method of the USMeta internal component.USMeta.ModulesAt runtime, gets metadata information about how modules are run. This information extends not just to consumed modules (if any) and plug-in modules (if any), but also to the application itself (the so-called "consumer application" or "main module").Returns an XML document of the form demonstrated in the Example below.The return document contains an entry for:The application itself (the "consumer application" or "main module"). Any module that has been declared for the application with Load Module = Yes. Any module that is run as a result of being declared as a plug-in module in a .PIN file.Each entry contains a list of attributes that are name/value pairs. Attributes returned are:Attribute Description MODULE_NAME The name of the module, or the name of the consumer application. VERSION For USoft applications, the USoft patch version name (for example, '10.0.1') of the module. For user-de

60
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Jobs

This article is about the Jobs method of the USMeta internal component.USMeta.JobsAt runtime, gets metadata information about jobs from the model developed in USoft Definer.For each retrieved job, this information takes the form of name/value pairs. Each name/value pair expresses a job attribute setting. In addition, this method returns information about input parameter sets and output parameter sets (if any).Returns an XML document of the form demonstrated in the Example below.SyntaxSELECT USMeta.Jobs(    job-name-pattern Jobs,   interfaces-only InterfacesOnly,   module-pattern Module,   mime-type MimeType)interfaces-only ::= { yes | no }mime-type ::= { application/xml , xml , application/json , json }All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The '.*import.*' value in the following example is for job-name-pattern because

40
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Domains

This article is about the Domains method of the USMeta internal component.USMeta.DomainsAt runtime, outputs metadata information about domains, data types and allowed values from the model developed in USoft Definer.Returns an XML document of the form demonstrated in Example at the end of this article.OutputDomainsFor each retrieved domain, the output takes the form of name/value pairs:Name Value NAME Domain Name MODULE_NAME If the domain is not from a consumed module: the current application name. If you are calling from a USoft application, this is the USoft application name, eg., USD for USoft Definer. If you are calling from a User Application, this is the User Application name, eg. SALES. If the domain is from a consumed module: the name of the consumed module. In this case the consumers are listed in a child element, see the note below this table. DATABASE_TYPE Data Type DISPLAY_DATATYPE Display Type. Values map to prompts as in the "Display types” table

210
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Decisions

This article is about the Decisions method of the USMeta internal component.USMeta.DecisionsAt runtime, gets metadata information about decisions from the model developed in USoft Definer.For each retrieved decision, this information takes the form of name/value pairs. Each name/value pair expresses a decision attribute setting.Returns an XML document of the form demonstrated in the Example below.SyntaxSELECT USMeta.Decisions(    decision-name-pattern Decisions,   interfaces-only InterfacesOnly,   module-pattern Module,   mime-type MimeType)interfaces-only ::= { yes | no }mime-type ::= { application/xml , xml , application/json , json }All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The '.*test.*' value in the following example is for decision-name-pattern because of the "Decisions" alias:SELECT USMeta.Decisions( '.*test.*

110
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Constraints

This article is about the Constraints method of the USMeta internal component.USMeta.ConstraintsAt runtime, gets metadata information about constraints from the model developed in USoft Definer. For each retrieved constraint, this information takes the form of name/value pairs. Each name/value pair expresses a constraint attribute setting.Returns an XML document of the form demonstrated in Example 1 below.SyntaxSELECT USMeta.Constraints(constraint-name-pattern Constraints, message-pattern Message, transition-table-pattern TransitionTable, mime-type MimeType)mime-type := { application/xml , xml , application/json , json }All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The 'ID' value in the following example is for constraint-name-pattern because of the "Constraints" alias:SELECT USMeta.Constraints( 'ID' Constraints

150
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Components

This article is about the Components method of the USMeta internal component.USMeta.ComponentsAt runtime, gets metadata information about components from the model developed in USoft Definer. This information covers general information about the component, methods, and parameters.Returns an XML document of the form demonstrated in the Example below.SyntaxSELECT USMeta.Components(name-pattern Components, architecture-pattern Architecture, interfaces-only InterfacesOnly, module-pattern Module, mime-type MimeType)mime-type ::= { application/xml , xml , application/json , json }All parameters are optional. Parameter values that you pass are mapped to parameters by alias name. The '.*DOT NET.*' value in the following example is for architecture-pattern because of the "Architecture" alias:SELECT USMeta.Components( '.*DOT NET.*' Architecture )This results in all components of

140
MaxMallon
1 year ago
MaxMallon
MaxMallon
published in USMeta internal component

USMeta.Columns

This article is about the Columns method of the USMeta internal component.USMeta.ColumnsAt runtime, gets metadata information about columns from the model developed in USoft Definer. For each retrieved table, this information takes the form of name/value pairs listed in the table below.In addition, as a nested child XML element, this method also delivers domain information as described in USMeta.Domains. This domain information takes the form of nested child XML elements,Returns an XML document as demonstrated in Example 1 below.Name Value TABLE_NAME Table Name COLUMN_NAME Column Name MODULE_NAME If the column is not in a table from a consumed module: the current application name. If you are calling from a USoft application, this is the USoft application name, eg., USD for USoft Definer. If you are calling from a User Application, this is the User Application name, eg., SALES. If the column is in a table from a consumed module: the name of the consumed module. U

460
MaxMallon
1 year ago
MaxMallon
MaxMallon

Constraints that fire on query/touchNew

It's an idea I've had for some time, but I'm not sure if it's useful. Now constraints can fire on insert, delete, or update. Would a constraint that fires whenever a certain column is queried or touched at all be useful? 

2
Harm Hofstee
2 years ago

Badge winners

Show all badges
Terms & ConditionsCookie settings