www.usoft.com To www.usoft.com

Replies posted by Rob.van.Haarst

7 Replies

Rob.van.Haarst
Rob.van.Haarst
published in Creating a USoft Production environment

Running a USoft application from a Linux container

Mmm I am certain that the command worked with double quotes in my environment at the time of writing. I cannot remember why I chose to write the double quotes.

2593
S
6 months ago
Rob.van.Haarst
Rob.van.Haarst
published in Rules Engine properties

AllowSetManipulations

De auto waarde regelt define-time dat de parameter op False komt te staan in C/S en RulesService, en op True in RunBatch. Als je zo'n default later (runtime) wilt beinvloeden via RulesEngine.SetProperty, dan zit je al IN een van die drie contexten, dus is 'auto’ niet meer nodig of van toepassing.Yes|No en True|False zijn equivalent, maar dat ze door elkaar gebruikt worden, is helaas slechte afwerking. Hier moeten we mee leren leven. Weliswaar kun je bij SetProperty de twee aanduidingen door elkaar heen gebruiken (je kunt middels 'False’ iets op ‘No’ setten), maar bij GetProperty krijg je helaas 'Yes|No’ terug terwijl de parameter zelf juist de True|False aanduiding gebruikt.Overigens viel mij op dat de betekenis van deze setting helemaal niet goed was uitgelegd, eigenlijk ook niet in eerdere documentatie. Ik heb geprobeerd dit te verbeteren (zie de nieuwe tekst in het artikel over de ALLOW_SET_MANIPULATIONS parameter), maar 100% begrijpen doe ik het nog niet. R

372
Rob.van.Haarst
1 year ago
Rob.van.Haarst
Rob.van.Haarst
published in BatchRunner internal component

BatchRunner.StartJob

StartJob will continue to be supported in USoft 10.x versions. No upgrade required.However, RunJob or a job method (ie., Batchrunner.<job-name>) have advantages over StartJob. You can pass typed parameters as opposed to flat strings, and you can call these components from constraint SQL.

903
R
1 year ago
marc
marc
asked in Got a Question?

Create a text file containing the release number in UDeliver

Yes, this takes some fiddling around I'm afraid."Mark up text file" is not suitable, this is meant for the very specific purpose of creating files with target variable placeholders. These are files that execute operations that will run with different var values on different target machines.There are two avenues leading to a solution here.1.UDeliver has a feature called "packing slip" (Du. 'pakbon') especially meant for releasing, with your deliverables, a descriptive XML file.One of the chief pieces of information in this file is the current release version number/name.Please search Community for "packing slip".2.If you want more freedom to customise, I would suggest you add a "Run SQL Command" task step that calls one of the USoft utilities for producing a flatfile on the file system.For example, you can execute: invoke xml.export with select select folder_label, 'file-path' WriteOutputTo from t_dl_release_frame where dl_current = 'Y'. Make sure you have UDELIVER declared as Applicati

2
marc
1 year ago
marc
marc
asked in Got a Question?

UDeliver action versions in USoft 10.0

Yes! This is intentional. When we created UDeliver in USoft 9.1, we anticipated that we might need to version the Actions in UDeliver, so that it would be relatively easy to introduce improved variants of the Actions without disturbing backward compatibility. So far, we have found that we do not need this mechanism. So, '9.1’ works equally on 9.1 and on 10.0.To remove confusion, for now, from 10.0.1F, we will stop displaying these version numbers in the UDeliver windows.But: we are preparing a simplification of the delivery of modules. This could lead, for the first time, to different versions of the same UDeliver Actions. If this happens, we will need to bring the version numbers back into view.

2
marc
2 years ago
marc
marc
asked in Got a Question?

USoft 10 Authorizer roles documentation

Hello marc,Thanks for these questions. You are completely right. There are a 2 things missing here.Your error message appears because the standard USD_DEVELOPER role misses access rights on table T_BUSINESS_PROCESS_STEP.  This is wrong: USD_DEVELOPER should have all access rights to this table. This has been reported as a bug (121440). It will be fixed in the next USoft 10.0 patch. This problem already existed in 9.1. But in 9.1, as a developer, you could manually add this right to the USD_DEVELOPER usergroup.This brings me to the next thing missing. As you say, USoft 10.0 documentation no longer explains about standard roles. Our thought was that in 10.0, the Description field for Roles was sufficient for Authorizer users to understand what rights each standard role contains. Please have a look at role descriptions in Authorizer: does this answer your questions?Because of the many changes in this area, I will write an overview Community article on standard roles and access rights in U

2
marc
2 years ago
marc
marc

USoft Delivery Manager integration with GitNew

Hi Dara and Marc,This is an interesting suggestion and part of a much larger discussion about sourcing. When USoft started out all those years ago, the idea was to have a central database repository, with some additional features for deliverables that really had to be files and not database records. But in 2021, we are in a reality where Git file-based repositories are the leading delivery model for business software, and USoft database repositories will just have to fit into this larger framework. UDeliver is a step in this direction, because it automates conversion from database repositories to file-based deliverables.More concretely, at USoft, when we create PDF documentation for our USoft Studio product, we use UDeliver to pull and push directly to and from Git, using task steps like the following.This solution uses RDMI components. The USWTW_WINFILES performs common file system operations such as building filepaths for copying, moving and deleting files and folders. The code for t

4
marc
2 years ago

Badge winners

Show all badges
Terms & ConditionsCookie settings