www.usoft.com To www.usoft.com

- - Knowledge base
Ideas
Events

Community
Search

Topics started by Rob.van.Haarst

934 Topics

Recently active

Most views Most replies

published in JavaScript

Promises for asynchronous Javascript

This article explains the idea of promises and tells you why and how to code .then(), .catch() and .finally() clauses in USoft web applications.It gives some explanation about USoft's udbPromise object and how it is different from Javascript's standard Promise object.Promises are a JavaScript feature that represents the eventual completion (or failure thereof) of an operation of an asynchronous nature.Promises make web applications more responsive. They use as much of the browser's execution capabilities as possible. Promises have been integrated into every aspect of the USoft Web API.Promises in USoft can lead to unexpected results that are difficult to debug. To avoid this, make sure that you can predict the way in which operations in .then() branches follow each other. For details, go to the Promises in USoft section of this article.A better alternative for asynchronous calls Promises in USoft How does a promise help you in USoft? Where USoft implements promises Upgrading to promise

published in Between business rules and implementations

Vocabularies in USoft Definer

See alsoFormulations in USoft DefinerA vocabulary is a body of shared concepts structured according to the relations between them.Practically, in USoft Definer 11, a vocabulary is a collection of formulations that is subject to automatic colour-coding and hyperlinking as a set of formulations that clarify each other.The intended use is that you map a single USoft Studio vocabulary to a single USoft Definer vocabulary. If you work in this way, vocabulary is only a background concept that you should not spend time over.If you import (synchronise) formulations from USoft Studio to USoft Definer, a vocabulary is automatically created and all the imported formulations are made part of it. You can view the Vocabulary record via the Teamwork, Preparation, Vocabularies menu option.The concept of vocabulary is introduced in USoft 11 to make it possible in the future to refer to multiple vocabularies from a single USoft Definer repository.

published in Domain and table internal components

table.GetInitialData

This article is about the table.GetInitialData method of table internal components.See alsoInitial Datatable.GetInitialDataReturns the initial data defined for table table.By default, a table does not have initial data. In practice, most tables do not have initial data.Syntax 1INVOKE table.GetInitialDataSyntax 2SELECT table.GetInitialData()ExampleThis gets initial data for a table named EVP_PARAMETER:SELECT evp_parameter.GetInitialData()

published in Between business rules and implementations

Formulations in USoft Definer

Viewing formulations in the USoft Definer tool Business Rules window Implementations windows Navigating formulations in the USoft Definer tool Creating formulations in the USoft Definer tool Preserving earlier Business Rules in a backup vocabulary Placing existing old-style Business Rules in a backup vocabulary Viewing old-style Business Rules in a USoft 10 window Migrating earlier Business Rules to USoft StudioA formulation in USoft is a carefully worded statement that expresses in natural language (English or Dutch) some term or definition or business rule that helps to clarify how a business is conducted:Formulations talk about the business of the organisation that the development team is creating a USoft application for. They express what the team understands or assumes about their client.As the example shows, formulations are colour-coded in a characteristic way. They take part of their meaning from surrounding terms, definitions and rules that you can find by clicking on some

published in Introducing repositories

Globally Unique Keys (G_U_Ks)

USoft stores Globally Unique Keys (G_U_Ks) in non-displayed columns in USoft applications such as USoft Definer.G_U_Ks are random generated sequences of alphanumeric characters. They surface in G_U_K columns when you export to XML or JSON, for example:<Tables> <T_TABLE TABLE_NAME="T1" ... G_U_K="7CBBA3A755064385B8018E2E428DE0A9"/> <T_TABLE TABLE_NAME="T2" ... G_U_K="CB2F4784303A4F5693FD2FB109496316"/></Tables>USoft has introduced G_U_Ks as a necessary element of USoft version control. As a developer, you do not need to know about the connection between the two.You can occasionally take advantage of G_U_Ks when you export and import data describing your own applications because G_U_Ks allow you to identify a record by a different means than the record's primary key value(s). This can be helpful when you update a primary key value in one environment and you want to repeat that update in a different environment. Why is this?To see how this works, first consider h

published in Version control

Version-controlled repositories

See alsoVersion control: CreateVersion control: ConnectVersion control: Synchronise, Temporarily Disable, DisconnectVersion-controlled USoft repositoriesAs you work on a USoft application, you gradually fill a repository of RDBMS tables with implementations. These are the source of the runtime application you deliver to end users.Your team can decide to bring this shared USoft development repository under a file-based version control system such as Git. In this arrangement, there is no central database. Instead, each team member holds his or her own local working copy of the USoft repository:Version-controlled USoft repositoryFor each team member, USoft version control keeps repository work in sync with a local Git tree. All team members are connected to a single, central, remote, shared Git tree. A team member pulls the latest version of the central Git tree before starting work. When finished, the team member pushes changes back to the central tree. The interaction between local tree

published in Version control

Version control: Create

See alsoVersion-controlled repositoriesVersion control: ConnectVersion control: Synchronise, Temporarily Disable, DisconnectTo bring a USoft application under version control for your team, you must first put it in place by taking explicit one-time action. This is referred to as Create.To create version control for a USoft application in Development:In the USoft application (USoft Definer, USoft Service Definer...) that you want to bring under version control, from the tool menu, choose Tools, Version Control, Version Control Configuration. This dialog appears: Click the Create button. Specify the file directory where you want the files for version control to be written to initially, then click Save. Inspect the result on the file system. See that files have been created for all objects in your repository. See also that at the top level, a file has been created named application.usv where ".usv" is for "USoft version control" and application is the abbreviated name of the USoft applic

published in Version control

Version control: Connect

See alsoVersion-controlled repositoriesVersion control: CreateVersion control: Synchronise, Temporarily Disable, DisconnectAs a team member in a USoft project, to start participating in a version-controlled USoft repository, you initially need to Connect to the version control arrangement.As a prerequisite, you need to have a locally installed RDBMS system or you need some way of connecting to a private location a remote database server.You also need to have the USoft tool set installed. Create a USoft Binder file where you specify the database connect string that points to your database (SQLServer) or database account (Oracle). Then, create an empty local USoft project. From USoft Binder, first create tables for USoft Authorizer. This creates an authorization layer that gives you access to the USoft tools. You now have an empty USoft development environment where you can participate in a shared, version-controlled USoft repository.Finally, you need to be connected to a Git (or other)

published in Version control

Version control: Synchronize, Temporarily Disable, Disconnect

See alsoVersion-controlled repositoriesVersion control: CreateVersion control: ConnectThis article describes how you work as a development team member with a version-controlled USoft repository.To do that, you must have Connected to such a repository as a one-time action.Pull, synchronize, pushOnce you are connected to a version-controlled USoft repository:Before you begin a chunk of work, pull the remote tree in Git (or other). Then, open the version-controlled USoft application (eg., USoft Definer). If any changes have been pulled that you do not yet have in your local USoft repository (the RDBMS tables), this dialog pops up when you open the application: All you need to do is press the Synchronize button to confirm. After you have finished a chunk of work, USoft will have automatically written this work to the local file tree. You are ready to push these changes so they become available to the whole team. This last step is not USoft-specific.Synchronize: TroubleshootingIf errors oc

published in EAR diagrams

How EAR diagrams map to Definer records

Overview Viewing an EAR diagram's properties Data contents of the Business Object Tables Tables: Definer-to-diagram Tables: Diagram-to-definer Columns Columns: Definer-to-diagram Columns: Diagram-to-Definer Parent-child relationships Parent-child relationships: Definer-to-diagram Parent-child relationships: Diagram-to-Definer Supertype-subtype relationships Supertype-subtype relationships: Definer-to-diagram Supertype-subtype relationships: Diagram-to-Definer OverviewEAR diagrams in USoft Definer 11 are automatically synchronised in both directions with records in USoft Definer for:Data contents of the Business Object that the EAR diagram is for. Tables. Columns. Relationships. Relationship columns.As a result of this 2-way synchronisation:When you open or re-open the EAR diagram from the Business Object, the diagram is automatically adjusted to the latest changes you made in USoft Definer for these objects. For example, if you added a Table in Definer, you will see a new table

published in EAR diagrams

How to draw objects in an EAR diagram

Setting up a canvas for an EAR diagram Drawing tables (or: entities) Adding a new free-floating table box Adding a new table box connected to an existing table box Dropping a table box Moving a table box Resizing a table box Drawing columns (or: attributes) Adding an attribute item Changing properties of an attribute item Changing the order of attributes in a table Dropping an attribute item Drawing relationships (or: relations) Adding a relationship Changing properties of a relationship Reversing the cardinality of a line Changing the position or shape of a relation line Dropping a relation line Setting up a canvas for an EAR diagramTo draw an EAR diagram, you first need to set it up. This works very differently between USoft 10 and USoft 11. For details on this, please go to the EAR diagrams article.Drawing tables (or: entities)Tables (or: entities) are represented in EAR diagrams by table boxes. A table box looks like this:Adding a new free-floating table boxTo add a ne

published in Object shopping

Importing from USoft Studio into USoft Definer 11

See also This import works only if your data come from USoft Studio 4.2. You can see the Studio version in the footer bar of Studio.We offer a workaround utility for exports from USoft Studio 4.1. Perform the following 2 temporary steps.We also offer a workaround utility for migrating earlier Business Rules from Definer (Teamwork) to Studio.To import data from USoft Studio 4.1:Apply the special Studio41ToStudio42.xsl utility transformation to your export file before you import:invoke uscsxsl.apply2file with select 'filepath\export.xml', 'usoft-installation-dir\xsl\Util\Studio41ToStudio42.xsl', 'filepath\export.xml'After import, in USoft Definer, choose Teamwork, Preparation, Vocabularies from the menu. Find the Vocabulary that the imported formulations belong to. In the Vocabulary record, manually add the URL leading to the origin of the formulations (this is a one-time action):Syntaxbase-url/pages/instance/app.usoft#p=Workspace&bid=projectbase-url is the same as when you log on to

published in Roles

DDL rights

DDL rights are the rights to Create, Alter and Drop database tables, that is, tables known to the RDBMS.In USoft, you need DDL rights in order to run the "Create Table” routine for any application, eg. Authorizer, Definer, or the User Application that you are developing.You grant or revoke DDL rights by setting the DDL Scope attribute.DDL rights are (for a given application) all-or-nothing, across-the-board rights. For an application, a role either has all DDL rights on all tables, or it does not have any DDL rights on any table. This makes “DDL Scope” an attribute of the role itself.If you run with merged roles, a user has DDL rights if-and-only-if he or she is assigned any role that has DDL Scope = Foreground-and-Background.If you do not run with merged roles, a user has DDL rights if his or her current role has DDL Scope = Foreground-and-background.A bootstrap problem would occur if nobody had the right to create tables in which to store the right to create tables. To prevent this

published in USCSXSL internal component

USCSXSL internal component

This article contains general information about the USCSXSL internal component.For an alphabetic list of USCSXSL methods, click here.What is it?The USCSXSL internal component is an XSLT 1.0 processor with rich extensions also found in XSLT 2.0 or 3.0. It is a USoft-proprietary C# implementation.The USCSXSL internal component gives you the same basic XSLT functionality as the USXSL component. This is to say that it provides a standard XSLT 1.0 processor and, in addition, the capability to mix in USoft application data.But in addition to the USXSL component, USCSXSL also allows you to call extension functions. You can discover these functions by calling ublendit.exe:> usoft-bindir\ublendit.exe functions> usoft-bindir\ublendit.exe functions ns=strings> usoft-bindir\ublendit.exe functions p=titleTo find out all about extension functions but also other Blend-related resources, go to Learning USoft Blend for repository management.Intended useUse this component in any way that you wo

published in Domains

Template domains: Popular domain settings

Importing and viewing template domains Creating a domain based on a template domain Changing a template domain Re-applying a template domain to a domain of your ownA template domain is a popular collection of domain settings provided by USoft. A template domain is usually appropriate for a typical base data type often found in USoft applications, such as "Short text” or “Boolean”.When you create a domain, you can optionally take one of the template domains and use it as a starting point for your own domain. To keep things simple, it's usually a good idea to introduce only minimal differences, or even no differences at all, between your new domain and the template. Introduce changes only if you have a specific reason.Template domains are not only a quick and convenient way of creating a domain of a specific type.They also play a role if you decide to create columns by drawing them in EAR diagrams.Here are the 9 template domains of USoft 11:Template domain Description BINARY Binary

published in RulesEngine internal component

RulesEngine.MessageLanguage

This article is about the MessageLanguage method of the RulesEngine internal component.RulesEngine.MessageLanguagePresents a USoft-defined or user-defined message in a box or dialog in an interactive setting, that is, in a setting involving a human interface. Translates the message into the runtime language if a translation in that language is available for the message.This method may be called from, eg., a SQL Task in a USoft Batch job.Web applicationsSyntaxSELECT RulesEngine.MessageLanguage ( category, name, type [, parameter ... ])type := [ INFORMATION | ERROR ]The required category is the category that the message belongs to, as specified in the System Messages record for the message. The required name is the logical name of the message as specified in the System Messages record for the message. Name is unique within the message category.The required type must be one of the following:INFORMATION Shows an information message. Processing continues. ERROR hows an error m

published in Understanding USoft

Release, upgrade and maintenance policy

Release and upgrade policy Major releases Minor releases Patch releases Maintenance policy Support policyRelease and upgrade policyUSoft has three kinds of releases. To understand how you upgrade to a new release, you need some understanding of these 3 levels.Major releasesMajor releases (eg., 10, 11, 12) contain new functionality, changes in existing functionality, and the removal of functionality deprecated in the previous major version.To move to the latest major release for the first time, you need to perform an upgrade procedure on the Development repository (on Definer, Delivery Manager, etc.). Sometimes you also need to perform an upgrade on Authorizer in acceptance and production environments.A major release is usually first brought out in 1 or 2 beta versions. A beta version is used to gather feedback from customers and developers about new features.In upgrades to major releases, most 3rd party software is updated to a recent version.When you upgrade to a major or minor rel

published in RulesEngine internal component

RulesEngine.SetRole

This article is about the SetRole method of the RulesEngine internal component.RulesEngine.SetRoleChanges the role on the basis of which the logged-on user has access to the application. This is the active role. On application entry, the active role is the user's default role.Calling this method if you are running in distinct-roles mode is an error. In merged-roles mode, the user has access to all her roles at all times.Calling this method is effective only if the logged-on user has been given multiple roles. In this case, she accesses the application on the basis of her default role. Calling the method allows switching to other roles. Access rights on tables, columns, components, and jobs, and the First Menu Page are changed accordingly.SyntaxSELECT RulesEngine.SetRole ( role)The required role is the name of the role being switched to. This must be one of the roles associated with the user in in USoft Authorizer.ExampleSELECT RulesEngine.SetRole ( 'REVIEWERS')

published in SQL syntax

Pseudo-columns

This article is about pseudo-columns as part of the SQL syntax that USoft supports.Pseudo-columnsA pseudo-column is an expression that you can use in the SELECT list of a SQL statement as if it were a column name, but that does not refer to a physical column in a table.You can use pseudo-columns in SELECT output lists but also as the value of certain attributes in USoft Definer, in particular, in the Default Value attribute of Columns and Domains.Pseudo-column Description ROWNUM The sequence number of a given record in a query result set. SYSDATE The current server date. SYSDATE is Oracle-only. For portability to other platforms, use $$CURRENTDATE$$ or the CURRENT_DATE SQL function instead. $$CURRENTDATE$$ The current server date. $$CURRENTDATETIME$$ The current server date and time. $$GUID$$ A generated GUID, same result as the GUID() SQL function. $$TRANSACTIONDATE$$ The server date of the first time this function is processed within the transaction. $$

published in Authentication and USoft

Front-end users and RDBMS users

This article is for USoft 11 only. For USoft 10, go to Account Funneling.RDBMS user Front-end users Authenticated by USoft Authenticated by the OS: Single sign-on (Windows Authentication) Authenticated by the RDBMS Disabling front-end user access In USoft web solutions, in Production, authentication of end users is typically performed by USoft. On behalf of end users, under the hood, USoft accesses the RDBMS using an RDBMS username/password combination. This has 2 distinct purposes:Enhanced security. Web users do not connect to the database directly. It is much harder to hack the application by SQL injection strategies. Ease of administration. DBAs need to grant and facilitate only a single RDBMS user.USoft 11 features a complete separation between, on the one hand, the RDBMS user responsible for database access, and on the other hand, front-end users. This distinction has been implemented for all applications: USoft applications: usd, creapp, runbatch, sqlscript, usclock, as well a

published in UDB Rowset

Rowset.executeQuery()

This article is about the executeQuery() function of the Rowset object.Rowset.executeQuery()Executes a query specifically for the rowset. Existing queried data (if any) is cleared before the query is executed.Returns a Promise object or the 'this' object. From USoft 10.0.1I, returns a udbPromise instead of a Promise object.Syntax$.row-set.executeQuery( options )options ::= { hostvars: hostvars, nocheck: nocheck, orderBy: order-by, before: before-function, promise: promise, success: success-function, error: error-function}hostvars ::= { name : value, ... }nocheck ::= { true | false }order-by ::= order-col, ...order-col ::= { col-name | col-sort-order }col-sort-order ::= { col-name : sort-order }sort-order ::= { ASC | DESC }promise ::= { true | false }For an explanation of options, please go to the $.udb(ds).executeQuery() article.Examplevar rowSet = $.udb(this.dsId).rowSet(pRef);rowSet.executeQuery().t

published in UDB Rows

Rows.rsc()

This article is about the rsc() function of the Rows object.Rows.rsc()Returns the rowset that the first element in the Rows object is connected to.This allows you to execute a query specifically for that row set.Examples$.udb('TEST').rows("current").rsc();$.udb('TEST').rows("current").rsc().executeQuery();

published in UDB Events

uploadcomplete

This article is about the uploadcomplete UDB event handler.uploadcompleteThis event may be called from web pages developed in Web Designer and processed by a USoft page engine service.Event Occurs when uploadcomplete When the front-end has received a signal from the server that a file has been successfully uploaded. How to useFind or create an Event Listener object with Event Type = uploadcomplete. Event Listeners are in the Web Designer Controls catalog:Insert the event listener into the data source object. Insert a callClientScript action into the event listener. Use this action's Script property to code the behaviour that you want to see when the event occurs.

published in Tables, columns and relationships

External tables

What is an external table?An external table is a table declared in USoft Definer as if it were a regular database table, but that in fact corresponds to an RDBMS view or an RDBMS synonym.Often, but not necessarily, external tables collect data that come from tables located at some distance of the USoft application. Often, but not necessarily, these data are read-only to the USoft application.How is an external table different to USoft?The fact that a table declared in USoft Definer exists in the RDBMS, but as a view or synonym and not as a physical table, means 2 things to USoft.Create Tables ignores external tablesCreate Tables routines automatically ignore external tables. They do not attempt to create,or drop and re-create, an external table.You can call a Create Tables routine from context menus in USoft Binder, from the Tools, Create Physical Tables option in the Definer menu, and by pressing the Create button in the Tables window of Definer.TDF features ignore external tablesThe

published in Creating a USoft Production environment

Running a USoft application from a Linux container

USoft from a Linux container Installing Docker Getting a USoft base image from the Azure Container Registry (ACR) Utility links for communicating with Docker Setting up the database connection "odbc.ini” file Utility links for setting up database access TCP/IP access Starting the Linux container running the Rules Service "RulesService-7777.config” file Creating and starting the container Adding file-based deliverables to the container Configuring the Rules Service Starting the Service Framework Browsing the solutionUSoft from a Linux containerUSoft delivers a Linux port of the following products:RulesService Service Framework UBlendItThis allows you to run these products from a Linux container. The Linux container is delivered in the form of a Docker image downloadable from an Azure registry.To obtain this image, contact USoft support to get a client-id and a client-secret. These credentials will allow you to pull (download) a recent image from the USoft Azure Container Registry

1
2
3
4
...
38

Page 1 / 38

Badge winners

Rens Kersbergenhas earned the badge Explorer
rene.de.bruinhas earned the badge Explorer
rene.de.bruinhas earned the badge Scout
Janhas earned the badge Explorer
kesselringjhas earned the badge Explorer

Show all badges

Powered by Gainsight

Terms & Conditions Cookie settings

Sign up for the USoft Community

Already have an account? Login

Username *

E-mail address *

First name *

Last name *

Company

Password *

I accept the terms & conditions

loginBox.register.email_repeat

Login into the USoft Community

No account yet? Create an account

Username or Email

Password

Remember me

Forgot password?

Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.

Username or e-mail

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

OK

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

OK

CONTACT

USoft B.V.
IJsselmeerweg 1
1411 AA Naarden
The Netherlands

+31 (0)35 699 0699
info@usoft.com
www.usoft.com

© Copyright 2024 Privacy Policy

EXPLORE MORE

About USoft
Working at USoft
Success stories