Difference: 530UserCancel (7 vs. 8)

Revision 82014-10-03 - AlKalter

Line: 1 to 1

META TOPICPARENT	name="Main.APPX530Features"

Interrupt Running Processes

Line: 17 to 17

When interrupting a running job, the End of Process event point is executed for all processes and control is returned to the user.

Changed:

<
<

In Application Design, the designer can use this keystroke to interrupt a running process and enter the debugger, even if a TRAP has not been previously set. To enable this capabilty while running outside of Application Design (ie, as a normal user), set the environment variable to APPX_DB_TRAPS to a non blank value.

>
>

In Role Based Security, there is a new flag at the Database, Department, Workgroup, Role and User levels that controls this Cancel ability (Cancel Ok?). You can clear this flag to indicate cancelling a running process is not allowed. This further restricts any designer specified cancel flags, but does not override them. In other words, checking this flag (Cancel Allowed) will not allow a process to be cancelled if the designer has specified the process cannot be cancelled. Clearing this flag (Cancel Not Allowed) will prevent any process from being cancelled, even if the designer has not specified the process cannot be cancelled. Leaving this as a '?' is the same as checking it. This flag can be specified at the Database, Department, Workgroup, Role and User levels. Lower levels take priority over higher levels, ie, a value specified at the User level will override a value at Role, Workgroup, Department and Database levels. If you leave it as a '?' at a lower level, then the higher level setting will apply.

Comments:

View topic | History: r8 < r7 < r6 < r5 | More topic actions...