Declaring context parameters
NOTE: You can only declare context parameter in modules.
Context parameters are utilized in things like automatically generated emails. These emails contain a link referencing a fixed point in the web application. This option removes step-by-step navigation in the application from the user.
Example: approving a request
A manager receives an email that an employee has been added and can request permissions. The email contains a link to a custom request page with preset data of the new employee.
To disable a context parameter for a module
NOTE: You have already selected a module. In the above example, the CCC_ITShop_Approvals module is used.
- In the definition tree view, click
and open the Configuration node.
- In the Context parameters subnode, select the UID_PersonWantsOrg data object.
Now you can edit the following settings for this context parameter in Node editor.
Table 61: Context parameter settings
| Identifier |
The name of the selected data object is preset. |
| Option "Mandatory parmeter". |
If this option is enabled, the parameter is mandatory. |
| Type |
Parameter type selection. |
| Comment |
Specifies how the parameter is used. |
- Modify settings, then click
.
Detailed information about this topic
Running Microsoft .NET Framework code
The web project defined in the Web Designer is translated by the compiler in C# language. This compiles the complete logic of the definition document into a Microsoft .NET Framework assembly. It is possible to incorporate your own C# source code into this procedure. This way, you have access to the complete functionality of the various executable layers. In this section, it will be explained how you incorporate your own C# source code.
Runtime API
Web Designer objects written in C# code can be integrated directly into the object definition. This makes customizing the web application very flexible.
The web project code uses the runtime API of the Web Designer. The runtime API provides the following functionality, which is required for running the web project.
- Managing database connections with VI.DB.dll
- Authenticating and authorizing HTTP traffic
- Web controls
- Debugging Web Designer interfaces
The following diagram exemplifies the layer structure of components from the web project to the database.
For detailed information about runtime API classes, see the OneIM_QBM_WebRuntime.chm file.
Figure 2: Structure from the web project to the database
Integrating code into object definitions
In the Web Designer, you can insert a C# code fragment into an object’s code using the Code fragment node type.
//------------------------------------------------------------------------------
// <auto-generated>
// This code is tool generated
// Runtime version:4.0.30319.34209
//
// Changes to this file may cause incorrect behavior and be overwritten when
// the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------
NOTE: Changes to the code remain intact even on regeneration when you make them in the Web Designer.
