DEV Community: zuUwn21

🔄 Uniface forlist...endfor: Mastering List Loops

zuUwn21 — Fri, 11 Jul 2025 21:44:48 +0000

📝 Introduction

As a Uniface developer, you frequently encounter the need to process lists. The forlist...endfor loop is a powerful tool in Uniface 10.4, designed exactly for this purpose. In this post, I'll explain how to use this loop effectively! 🚀

🎯 What is forlist...endfor?

The forlist...endfor statement defines a loop that processes all items in an indexed list. It's available in all Uniface component types and provides an elegant solution for list processing.

📋 Syntax

forlist Item {, Index} in SourceList 
  Your ProcScript 
endfor

🔧 Parameters in Detail

Parameter	Data Type	Description
Item	String	Current list item
Index	Number	Item number in list
SourceList	String	Variable or field containing Uniface (Gold-separated) list

⚙️ How it Works

The loop functions as follows:

🔄 Iteration: Each time the loop reaches endfor, Item and Index (if defined) are incremented
🛑 Termination Conditions: The loop stops when:
- Item number > last item number
- Index > last item number
- A break statement is encountered
📊 Index Value After Loop: Index = last item number + 1 (or position at break)

💡 Practical Example

Here's a concrete example that searches for "Pompey" in a list of ancient cities:

variables
    string vList
    string vItem
    numeric vIndex
endvariables

vList = "Athens;Rome;Syracuse;Pompey;Sparta"

forlist vItem, vIndex in vList
    if (vItem = "Pompey")
        putmess "Loop processing stopped on Item number: %%vIndex, Value: %%vItem"
        break
    endif
    putmess "Processing Item number: %%vIndex, Value: %%vItem"
endfor

📤 Output:

Processing Item number: 1, Value: Athens
Processing Item number: 2, Value: Rome
Processing Item number: 3, Value: Syracuse
Loop processing stopped on Item number: 4, Value: Pompey

🎯 Best Practices

✅ Do's:

Manipulate Index: You can change the Index within the loop for conditional control
Use Break: Utilize break for early termination when finding values
Meaningful Variable Names: vItem and vIndex are self-explanatory

❌ Don'ts:

Avoid Infinite Loops: Pay attention to correct termination conditions when manipulating Index
Consider Performance: For very large lists, consider alternative approaches

🚀 Advanced Use Cases

🔍 Search and Replace:

forlist vCurrentItem, vCurrentIndex in vDataList
    if (vCurrentItem = vSearchValue)
        ; Replace or process found value
        break
    endif
endfor

📊 Data Validation:

forlist vItem, vIndex in vInputList
    if (!$numeric(vItem))
        putmess "Invalid value at position %%vIndex: %%vItem"
        vHasErrors = 1
    endif
endfor

🎯 Conclusion

The forlist...endfor loop is an indispensable tool for every Uniface developer. It provides a clean, readable solution for list processing and enables complex processing logic through its flexibility.

Try it out and let me know in the comments how you use forlist in your projects! 💬

📚 Based on: Uniface 10.4 Documentation (Last Updated: June 20, 2024)

🤖 This post was created with AI assistance

# 🐛 Uniface Debugging: The `debug` Statement Explained

zuUwn21 — Fri, 11 Jul 2025 21:20:22 +0000

🚀 What is the `debug` Statement?

As a Uniface developer, you're certainly familiar with the challenges of debugging complex applications. The debug statement is a powerful tool that helps you step through your components and identify issues systematically.

📋 Basics

Syntax: debug
Return Values: None
Usage: Allowed in all Uniface component types

🔧 How Does It Work?

The debug statement puts your component into debug mode:

🖥️ GUI Environment

Starts the Uniface Debugger
Enables entering debugging commands
Provides a complete graphical interface

💻 Character Mode

Shows a debug command line at the bottom of the screen
Works in text-based environments as well

🎯 Practical Application

Standard Implementation

;Exec trigger
debug
edit
end ; end trigger

📱 Development vs. Production Environment

During development, it's common to place the debug statement in the Switch Keyboard trigger at the application level:

trigger keyboardSwitch 
if ($logical("SwitchKeyboard") = "debug")
 debug
endif
end

⚠️ Important Note: The statement should be removed before production or embedded in a conditional instruction!

🏢 Server Debugging

🚫 Limitations

The debug statement is not implemented for the Uniface Server:

The Debugger is neither started nor stopped
Windows server processes cannot start windowing applications that need a desktop to run on

💡 Solution for Server Debugging

Start the Debugger before the server (manually or via Uniface Router)
For remote debugging: Configure a unique TCP port for communication

🔧 Enabling Debugging in Deployed Applications

For the rare case when you need to debug in a production application:

Step 1: Add ProcScript

trigger keyboardSwitch 
if ($logical("SwitchKeyboard") = "debug")
 debug
endif
end

Step 2: Modify Assignment File

[LOGICALS]
SwitchKeyboard=debug

Step 3: Activate Trigger

Press GOLD Y to start the debugger.

🔄 Alternative: The /deb Switch

You can also use the /deb switch to start the application together with the Debugger. This is particularly useful for systematic debugging from the beginning.

🎉 Conclusion

The debug statement is an indispensable tool for every Uniface developer. It enables you to:

✅ Step through code line by line
✅ Inspect variables at runtime
✅ Use flexible debugging strategies
✅ Debug both locally and remotely

💡 Tip: Use conditional debug statements during development and remove them before production for optimal performance!

This article was created with AI assistance and is based on the official Uniface 10.4 documentation. Do you have questions or additional tips for Uniface debugging? Feel free to share them in the comments! 🚀

# 🚀 Uniface call Statement: Executing Functions and ProcScript Modules

zuUwn21 — Fri, 11 Jul 2025 20:49:09 +0000

This post is based on Uniface 10.4 documentation and was created with AI assistance 🤖

As a Uniface developer, you'll inevitably encounter the call statement - a powerful tool for executing functions and global ProcScript modules. Here's a comprehensive explanation of this essential command! 💡

📝 Basic Syntax

call {Library::}LitFunctionName { ( ArgumentList ) }

Example

call myFunction

🔧 Parameters in Detail

Parameter	Data Type	Description
Library	Literal	Library containing the global ProcScript module. If not specified, the default library is used 📚
LitFunctionName	Literal	Name of the module (without quotation marks!)
ArgumentList	String	Comma-separated list of arguments. Must match the number and type of parameters defined in the function

🔄 Automatic Type Conversion

If the data type of an argument doesn't match the corresponding parameter type, Uniface automatically attempts to convert the data to the proper type. This makes the call statement quite flexible in handling different data types! 🎯

🎯 Return Values and Status

$status Values

-1 ❌ Error occurred (details in $procerror)
0 ⚪ No value assigned or no return statement
>0 ✅ Successful return value from the function

🚨 Common Errors in $procerror

-1109 (UPROCERR_FUNCTION): Function not found
-1113 (UPROCERR_PARAMETER): Invalid parameter name or not defined
-1122 (UPROCERR_NARGUMENTS): Wrong number of arguments

Note: When a call succeeds, $procerror is typically cleared or contains no error information.

🔄 Understanding Parameter Directions

IN Parameters

Accepts: Constants, fields, indirect field references, variables, functions
Behavior: Value is transferred to the module's parameter at function start 📥

INOUT Parameters

Accepts: Fields, indirect field references, variables, assignable functions
Behavior: Value is transferred at start AND the function's end value is returned to the original location 🔄

OUT Parameters

Accepts: Fields, indirect field references, variables, assignable functions
Behavior: Only the function's end value is returned to the original location 📤

Important: If an error occurs (status = -1), values of OUT and INOUT parameters must be considered undefined in the calling component.

🎯 Practical Example from Real Usage

function LSTORE
    store
    if ($status < 0)
        message "Store error!"
        rollback
    else
        message "Store done."
        commit
    endif
end ; LSTORE

trigger store
    call LSTORE
    return ($status)
end; store

trigger accept
    if ($formdbmod = 1)
        call LSTORE
    endif
    return ($status)
end; accept

🔍 Understanding Module Resolution

Uniface searches for modules in the following order:

For Local Functions

Local functions in the component's triggers

For Global ProcScript (when no library specified)

Component library
Library specified in application shell properties
SYSTEM_LIBRARY

For Global ProcScript (when library specified)

If Uniface cannot find the module in the specified library, it stops searching and returns an error - no fallback to other locations! 🚫

For detailed information about the search process, refer to the Compilation Process documentation.

💡 Best Practices and Tips

✅ Do's

Use descriptive function names
Always check the $status value after the call
Match parameter count and types exactly
Handle potential type conversion scenarios

❌ Don'ts

Don't put LitFunctionName in quotation marks
Avoid returning -1 from your functions (reserved for system errors)
Don't ignore parameter direction requirements
Don't use call for global ProcScripts in self-contained services/reports

⚠️ Structure Editor Consideration

Important: The $status value can affect how the structure editor behaves when activating trigger sequences. When calling functions in triggers, ensure the returned value doesn't adversely impact the structure editor's operation.

🎪 Availability

The call statement is available in all component types!

Exception: Calling global ProcScript modules is not allowed in self-contained services and reports. 🚫

🎉 Conclusion

The call statement is an indispensable tool for modular Uniface development. With proper understanding of parameter directions, automatic type conversion, error handling, and module resolution, you can create robust and maintainable applications!

Understanding these nuances will help you avoid common pitfalls and write more reliable Uniface code.

Do you have questions about Uniface or other development topics? Let me know in the comments! 💬

JSON-to-Struct with Uniface 10.4 jsonToStruct: A Practical Guide 📄⚡

zuUwn21 — Fri, 11 Jul 2025 20:09:17 +0000

What is jsonToStruct? 🤔
The jsonToStruct statement in Uniface is a ProcScript function that converts JSON text into a Uniface structure (Struct). This function is particularly valuable when receiving data from web APIs or processing JSON files.

Basic Syntax

jsonToStruct StructTarget, JsonSource

Parameters:

StructTarget:
Variable, parameter, or non-database field to hold the generated structure
JsonSource:
JSON text as string, variable, field, or filename

Practical Example 💻
Here's a simple example of how the function is used:

variables
    vStruct : struct
    vJsonText : string
endvariables

vJsonText = '{"name": "John Doe", "age": 30, "skills": ["C#", "Uniface", "SQL"]}'
jsonToStruct vStruct, vJsonText

; Accessing the data
putmess vStruct->name        ; Output: John Doe
putmess vStruct->age         ; Output: 30
putmess vStruct->skills->{1} ; Output: C#

Understanding JSON Structures 📊
JSON can have two main forms:

JSON Objects
Use curly braces { } and contain key-value pairs:

{
  "name": "Developer",
  "experience": 5,
  "active": true
}

Struct members are addressable by name: vStruct->name

JSON Arrays
Use square brackets [ ] and contain indexed values:

["JavaScript", "Python", "C#", "Uniface"]

Array elements are addressable by index: vStruct->*{1} (first element)

Data Type Mappings 🔄
Uniface automatically recognizes JSON data types and maps them accordingly:

JSON Type	Uniface Struct Annotation
string	jsonDataType = "string"
number	jsonDataType = "number"
boolean	jsonDataType = "boolean"
null	jsonDataType = "null"

Error Handling ⚠️
The function returns various status codes:

statuc code	descritption
0	Conversion successful
-4	File could not be opened
-13	Filename too long
-1900	JSON string empty or invalid
-1901	JSON text doesn't start with { or [
-1902	Parser error

jsonToStruct vStruct, vJsonFile

if ($status < 0)
    putmess "Error parsing: " ; $procerror
else
    putmess "JSON successfully converted!"
endif

Working with Files 📁
The function can also process JSON files directly:

jsonToStruct vStruct, "data.json"

Important Note: The file must be Unicode-encoded. If not, use fileload to first read the file into a variable.

Advanced Features 🔧

Struct Annotations
Uniface automatically adds metadata that provides information about the JSON structure:

jsonClass: Type of JSON construction (object or array)
jsonDataType: Data type of the struct member

Character Handling
During conversion, line breaks are normalized:

\r (Carriage Return) and \n (Linefeed) are converted to \r

When converting back with structToJson, CR characters are written as \n

Best Practices 🎯

Always implement error handling: Check the $status value after each conversion
Consider file format: Ensure JSON files are Unicode-encoded
Test complex structures: For nested JSON objects, test access paths beforehand
Documentation: Comment complex JSON structures for better maintainability

Comparison with Other Languages 🌐
Other programming languages have similar functions:

JavaScript: JSON.parse()
Python: json.loads()
C#: JsonSerializer.Deserialize()

What makes Uniface's jsonToStruct special is its seamless integration into the Uniface development environment and automatic struct generation.

Conclusion 🎉
The jsonToStruct function is a powerful tool for Uniface developers that significantly simplifies working with JSON data. It offers:

Simple syntax for quick implementation
Automatic type recognition for various JSON data types
Robust error handling for production-ready applications
Flexible data sources (strings, variables, files)

For anyone working with Uniface and needing to process JSON data, this function is definitely worth a closer look. It makes integrating web APIs and processing modern data formats much easier.

Have you already had experience with jsonToStruct? Share your tips and tricks in the comments! 💬

Transparency Note: This post was completely generated with AI, based on the Uniface Documentation 10.4. The prompts, ideas, and content direction come from the author to ensure a practical and understandable presentation of the technical concepts.

Uniface Date Functions 101 📅✨

zuUwn21 — Sun, 06 Jul 2025 09:36:31 +0000

Working with dates is a daily challenge in software development—whether it’s contract durations, deadlines, or recurring billing cycles. Uniface offers several handy functions to make date handling a breeze. In this post, I’ll introduce you to the essential date functions in Uniface, complete with practical examples and tips! 🚀

Why Are Date Functions So Important? 🤔

Process Automation: Automatically extend contracts, calculate deadlines, and trigger reminders—all based on dates.
Error Prevention: Manual calculations are prone to mistakes. Built-in functions keep your logic safe and reliable.
Internationalization: Handle different date formats and time zones correctly.

The Most Important Date Functions in Uniface 🛠️

Uniface provides several built-in functions for date manipulation. Here are the key players:

Function	Description
`$date`	Converts a string to a Uniface date
`$datim`	Returns the current date and time in Uniface format
`addmonths`	Adds or subtracts months to/from a date

1. `$date` – Convert Strings to Date Values 🗓️

With $date, you can turn a string like "28-feb-90" into a real Uniface date value.

myDate = $date("28-feb-90")

Tip: Always use $date when working with date strings to avoid formatting issues! 😉

2. `$datim` – Get the Current Date and Time ⏰

$datim gives you the current date and time in Uniface format.

currentDateTime = $datim

Perfect for timestamps, logs, or automated calculations.

3. `addmonths` – Add or Subtract Months ➕➖

addmonths lets you easily add or subtract months from a date. The result is stored in the system variable $result.

addmonths 1, $date("28-feb-90")
; $result = 28-mar-90

You can also use negative values:

addmonths -1, $date("28-feb-90")
; $result = 28-jan-90

Common Pitfalls and Best Practices ⚠️✅

Watch Date Formats: String interpretation depends on your locale settings. Always use $date!
Month End Handling: Without a reference date, month ends may “shift.” Use a reference date to keep patterns consistent.
Time Zones & Language Settings: Different settings can lead to unexpected results.

Conclusion 🎉

With Uniface’s date functions, you’re well-equipped to handle even complex date requirements elegantly and reliably. Use $date, $datim, and addmonths to make your applications more robust and flexible!

Curious for more?

In the next post, we’ll dive deeper into the addmonths function, exploring special cases, best practices, and common pitfalls. Stay tuned! 😎

What date challenges have you solved in Uniface? Share your experiences in the comments! 💬

Note: I used an AI assistant to help create and review this post. 🤖

# 🏁 Uniface 10.4: Summary, Best Practices & Resources for the activate Statement

zuUwn21 — Sun, 06 Jul 2025 09:19:24 +0000

🎯 Conclusion: activate as the Key to Flexible Uniface Development

The activate statement is the central tool for executing operations on component instances in Uniface. It offers you:

Flexibility: Dynamically call operations synchronously, asynchronously, or statelessly.
Error Control: Return values and error codes enable robust error handling.
Modularity: By passing parameters, lists, and entities, you can elegantly model complex scenarios.

🏆 Best Practices for activate

Always check $status and $procerror:

This lets you detect errors early and react appropriately.
Use qualifiers consciously:

Apply /async, /stateless, or /list as needed to achieve the desired execution mode.
Call operations with variables:

This increases the reusability and flexibility of your code.
Avoid negative return values:

In your own operations, avoid returning negative values, as Uniface interprets these as errors.
Use exception handling:

Utilize try/catch to catch and handle exceptions cleanly.
Always check parameters and arguments:

The number and type of arguments must match the declared parameters.

📚 Further Resources

Official Uniface 10.4 Documentation: docs.rocketsoftware.com
Uniface Community & Forum: community.rocketsoftware.com
dev.to Tags: #uniface #programming #tutorial #error-handling

🙌 Thank You & Feedback

I hope these posts help you use activate safely, flexibly, and effectively!

What are your experiences with activate? What best practices do you use? Share your tips and questions in the comments! 👇

This series was created with AI support and based on the official Uniface 10.4 documentation.

# ⚡ Uniface 10.4: Advanced activate Examples & Special Cases

zuUwn21 — Sun, 06 Jul 2025 09:12:06 +0000

🧑‍💻 Complex Usage Examples

1️⃣ Operations with Variable Names

You can dynamically pass the operation name as a variable:

Code:

$vOperation$ = "do_it"
activate "myCptInstance".$vOperation$()

Or with a local variable:

vOperation = "do_it"
activate "myCptInstance"."%%vOperation%%%"()

2️⃣ Passing Typed Lists with `/list`

With /list, you can pass multiple parameters as typed lists, e.g., for service operations:

Code:

putitem vInParms, -1, $date(20250101)
putitem vInParms, -1, $number(5)
activate/list "SERV2".ADD_WEEK(vInParms, vOutParms)

After the call, vOutParms contains the result.

3️⃣ Working with Entities and Occurrences

You can pass entire entities or occurrences to an operation:

Code:

setocc "PO_ITEMS", -1
activate "SERV2".TOTAL_LNS("PO_ITEMS")

🖥️ Special Cases & Noteworthy Features

Modal Forms

Only certain operations can be activated in modal forms.
The EXEC operation can be started from outside, others mostly only internally.

Code:

activate "MyModalForm"

Executing Operating System Commands

With a special service signature, you can start OS commands via activate:

Code:

activate "OS_SERVICE".COMMAND("dir C:")

Exception Handling

If an activated operation throws an exception, it is propagated to the activate statement.

You can use try/catch to handle errors:

Code:

try
    activate "MyCpt".do_it()
catch
    message "Exception: " + $procerror
endtry

📝 Practical Tips

Use variables for operation names to keep your code flexible.
With /stateless, you can call services statelessly and efficiently.
Always check $status and $procerror after every activate call for robust error handling.

This post is based on the official Uniface 10.4 documentation and was created with AI support. For details, see the original documentation.

What special cases have you solved with activate? Share your experiences in the comments! 👇

# 🛡️ Uniface 10.4: Return Values & Error Handling with activate

zuUwn21 — Sun, 06 Jul 2025 08:56:52 +0000

📊 Key Return Values

After calling an operation with activate, Uniface provides return values that help you assess the result and detect any errors.

`$status` – The Main Return Value

> 0: Successful execution, value returned by the operation.
0: No value assigned or no return statement present.
< 0: An error occurred; details are in $procerror.
9: User exited the form with ^ACCEPT.
10: User exited the form with ^QUIT.

Code Example:

activate "MyCpt".do_it()
if ($status < 0)
    message "Error: " + $procerror
endif

🚨 Error Handling with `$procerror`

If an error occurs, $procerror contains a specific error code. The most important codes:

Error Code	Meaning
-50	Component not found
-59	Operation not defined
-1122	Wrong number of arguments
-155	Instance could not be created
...	See documentation for more

Code Example:

activate "MyCpt".do_it()
if ($status < 0)
    selectcase $procerror
        case -50
            message "Component not found!"
        case -59
            message "Operation does not exist!"
        case -1122
            message "Wrong number of arguments!"
        case else
            message "Unknown error: " + $procerror
    endselectcase
endif

🧰 Best Practices

Always check $status and $procerror: Evaluate these values after every activate call.
Provide meaningful error messages: Use error codes to give targeted feedback.
Avoid negative return values: In your own operations, avoid returning negative values, as Uniface interprets them as errors.

🕵️‍♂️ Common Pitfalls

Wrong arguments: Number or type does not match the operation’s parameters.
Incorrect instance or operation name: Typos lead to -50 or -59.
Asynchronous calls: No OUT/INOUT parameters and no return value with /async.

📝 Example: Robust Error Handling

Code Example:

activate "MyService".calculate(100, 200)
if ($status < 0)
message "Error during call: " + $procerror
return
endif
message "Calculation successful! Result: " + $status

This post is based on the official Uniface 10.4 documentation and was created with AI support. For details, see the original documentation.

# 🏷️ Uniface 10.4: Qualifiers and Parameters of the activate Statement

zuUwn21 — Sun, 06 Jul 2025 08:39:03 +0000

🚦 What are Qualifiers in activate?

Qualifiers are optional switches that let you control the behavior of the activate statement. They determine how and in which mode an operation is executed on a component instance.

Overview of the Most Important Qualifiers

Qualifier	Meaning
`/list`	Passes input and output parameters as typed Uniface lists.
`/stateless`	Invokes the operation statelessly (creates a temporary instance that is deleted after execution).
`/async`	Executes the operation asynchronously (no OUT/INOUT parameters, no return value).
`/sync`	Executes the operation synchronously (default behavior).

Code Example:

activate /async "MyCpt".do_it(vArg1, vArg2)

The operation do_it is called asynchronously.

🧩 The Parameters of the activate Statement in Detail

Every activate statement consists of several components that you can use as needed:

Parameter	Type	Description
InstanceName	String	Name of the component instance (max. 16 characters). If not found, the instance is created.
OperationName	Literal	Name of the operation to execute (e.g., exec, accept, quit, or a named operation).
ArgumentList	String	Comma-separated list of arguments matching the operation's parameters.

InstanceName

Specifies on which component instance the operation is executed.
If the instance does not exist, it is created automatically.

Code Example:

activate "myCpt"

OperationName

Name of the operation to execute.
Can be specified as a literal or a variable.
If no name is given, .exec() is used by default.

Code Example (Literal):

activate "myCptInstance".do_it()

Code Example (Variable):

$vOperation$ = "do_it"
activate "myCptInstance".$vOperation$()

activate "myCptInstance".do_it()

Code Example (Variable):

$vOperation$ = "do_it"
activate "myCptInstance".$vOperation$()

ArgumentList

Comma-separated list of values passed to the operation.
The number and type of arguments must match the operation's declared parameters.
Uniface automatically converts data types when possible.

Code Example:

activate "myCptInstance".do_it(42, "Test")

📝 Tips for Using Qualifiers and Parameters

/list: Use this qualifier when you want to pass multiple input and output values as lists.
/stateless: Ideal for one-time, stateless calls—e.g., for services.
/async: Use asynchronous calls when you don’t need return values and the operation should run independently.
Parameter passing: Make sure the arguments match the number and type of the operation’s declared parameters.

💡 Practical Examples

1️⃣ Passing Typed Lists with /list

Code:

putitem vInParms, -1, $date(20250101)
putitem vInParms, -1, $number(5)
activate/list "SERV2".ADD_WEEK(vInParms, vOutParms)

Note: This post was created with AI support and based on the official Uniface 10.4 documentation. For further details, please refer to the original documentation.

Do you have questions or your own tips about qualifiers and parameters? Share them in the comments! 👇

2️⃣ Stateless Call with /stateless

Code:

activate /stateless "MyService".calculate(100, 200)

3️⃣ Asynchronous Call

Code:

activate /async "MyCpt".start_long_task()

🚀 Uniface 10.4: Introduction to the activate Statement

zuUwn21 — Sun, 06 Jul 2025 04:42:13 +0000

✨ What is the activate Statement?
The activate statement is a central element in Uniface for executing operations on component instances. It allows you to specifically call functions (operations) of a component at runtime—whether synchronously, asynchronously, stateless, or with special parameters.

Whether you want to start a form, call a service, or exchange data between components: activate is the key to flexible and dynamic control of your Uniface applications.

🛠️ Basic Syntax
The syntax of activate is flexible and powerful. Here is the basic pattern:

activate {/list | /sync | /async} { /stateless}
InstanceName{.OperationName (ArgumentList)}

InstanceName: Name of the component instance on which the operation is executed.

OperationName (optional): Name of the operation to be executed. If nothing is specified, .exec() is used by default.

ArgumentList (optional): Comma-separated list of arguments for the operation.

📦 Simple Practical Examples
1️⃣ Execute the Standard Operation on a Component

activate "MyCpt1"

Starts the standard operation (exec) of the component MyCpt1. If the instance does not yet exist, it is automatically created.

2️⃣ Call a Specific Operation with Parameters

activate "MyCpt1".do_it(42, "Test")

Calls the operation do_it on the instance MyCpt1 with the parameters 42 and "Test".

3️⃣ Instance is Automatically Created
If you address an instance with activate that does not yet exist, it is automatically created—without the need for an explicit newinstance command. This makes activate especially flexible and easy to use.

🧑‍💻 When and Why Should You Use activate?
Dynamically Start Components: You can flexibly call components and their operations at runtime.

Parameter Passing: Arguments can be specifically passed to operations.

Automatic Instance Creation: No separate newinstance needed; activate handles this for you.

Error Handling: You can respond to the result of the operation via return values and error codes.

Note: This post was created with the support of AI and based on the official Uniface 10.4 documentation. For further details, please refer to the original documentation.

Questions, suggestions, or your own activate tips? Feel free to share them in the comments! 👇

Uniface: How to Display a Simple Message in a Window 😊

zuUwn21 — Sun, 29 Jun 2025 09:45:59 +0000

Hello everyone! 👋

Today I want to share a small but useful tip from my work with Uniface. Maybe you’ve encountered this situation: you want to display a message in a window when starting a service—for example, to greet the user or provide important information.

After some experimenting, I found out how to do this easily! 🛠️

The Code: It’s That Simple!
Uniface allows you to display a message in an operation. The Init operation is always executed first when a service starts. That’s exactly where I added the following line:

public Operation Init

  askmess "Hello World"

end

With the askmess command (which means “ask message”), you can display a message dialog without much effort. In my example, “Hello World” appears when the service starts—but of course, you can use any text you like. 😃

Why Is This Useful?
Especially during development or testing, it’s helpful to get immediate feedback when a service starts. This way, you instantly know that the service was initialized correctly—or you can provide important information to the user.

Conclusion
Sometimes it’s the little things that make a developer’s life easier. I hope this tip helps you as much as it helped me! 👍

PS:
I created this blog post with the help of an AI (artificial intelligence). That way, I can share interesting content with you even faster and more efficiently! 🤖

Uniface for Beginners: How to Properly Define Numeric Parameters

zuUwn21 — Tue, 20 May 2025 06:08:53 +0000

Hello together,

During my search with the AI Perplexity, I did not find good results to determine how to specify a number as a parameter or as a variable in Uniface. Although there is Uniface documentation [1] on this, it was not found. I do not understand why the AI cannot find the definition of a number in Uniface, even though there is a source for this.

To make the best of it, I decided to write down my thoughts here. I do not consider myself a Uniface Senior or some kind of specialist in Uniface but rather as a beginner in this programming language.
In the past, when I had questions about a problem with a programming language like Java or C#, I used the search engine Google. Currently, due to the hype around ChatGPT, I use more of an AI like ChatGPT or Perplexity. Unfortunately, both provide me with rarely good results for the programming language Uniface, as there is too little source code and too few contributions on the internet about this.

Regarding the question of how to represent a number in Uniface, the answer is the following:

params numeric pPrice, pQuantity, pTotal : IN endparams pTotal = pPrice * pQuantity

Taken from the documentation of Uniface.

I hope I could help you a little bit with this problem and share my thoughts with you to show that you might not be the only one with this problem.

[1] https://docs.rocketsoftware.com/de-DE/bundle/uniface_104/page/yeo1699862389212.html

DEV Community: zuUwn21

🔄 Uniface forlist...endfor: Mastering List Loops

📝 Introduction

🎯 What is forlist...endfor?

📋 Syntax

🔧 Parameters in Detail

⚙️ How it Works

💡 Practical Example

📤 Output:

🎯 Best Practices

✅ Do's:

❌ Don'ts:

🚀 Advanced Use Cases

🔍 Search and Replace:

📊 Data Validation:

🎯 Conclusion

# 🐛 Uniface Debugging: The `debug` Statement Explained

🚀 What is the debug Statement?

📋 Basics

🔧 How Does It Work?

🖥️ GUI Environment

💻 Character Mode

🎯 Practical Application

Standard Implementation

📱 Development vs. Production Environment

🏢 Server Debugging

🚫 Limitations

💡 Solution for Server Debugging

🔧 Enabling Debugging in Deployed Applications

Step 1: Add ProcScript

Step 2: Modify Assignment File

Step 3: Activate Trigger

🔄 Alternative: The /deb Switch

🎉 Conclusion

# 🚀 Uniface call Statement: Executing Functions and ProcScript Modules

📝 Basic Syntax

Example

🔧 Parameters in Detail

🔄 Automatic Type Conversion

🎯 Return Values and Status

$status Values

🚨 Common Errors in $procerror

🔄 Understanding Parameter Directions

IN Parameters

INOUT Parameters

OUT Parameters

🎯 Practical Example from Real Usage

🔍 Understanding Module Resolution

For Local Functions

For Global ProcScript (when no library specified)

For Global ProcScript (when library specified)

💡 Best Practices and Tips

✅ Do's

❌ Don'ts

⚠️ Structure Editor Consideration

🎪 Availability

🎉 Conclusion

JSON-to-Struct with Uniface 10.4 jsonToStruct: A Practical Guide 📄⚡

Uniface Date Functions 101 📅✨

Why Are Date Functions So Important? 🤔

The Most Important Date Functions in Uniface 🛠️

1. $date – Convert Strings to Date Values 🗓️

2. $datim – Get the Current Date and Time ⏰

3. addmonths – Add or Subtract Months ➕➖

Common Pitfalls and Best Practices ⚠️✅

Conclusion 🎉

# 🏁 Uniface 10.4: Summary, Best Practices & Resources for the activate Statement

🎯 Conclusion: activate as the Key to Flexible Uniface Development

🏆 Best Practices for activate

📚 Further Resources

🙌 Thank You & Feedback

# ⚡ Uniface 10.4: Advanced activate Examples & Special Cases

🧑‍💻 Complex Usage Examples

1️⃣ Operations with Variable Names

2️⃣ Passing Typed Lists with /list

3️⃣ Working with Entities and Occurrences

🖥️ Special Cases & Noteworthy Features

Modal Forms

Executing Operating System Commands

Exception Handling

🚀 What is the `debug` Statement?

1. `$date` – Convert Strings to Date Values 🗓️

2. `$datim` – Get the Current Date and Time ⏰

3. `addmonths` – Add or Subtract Months ➕➖

2️⃣ Passing Typed Lists with `/list`

`$status` – The Main Return Value

🚨 Error Handling with `$procerror`