RPC HELP App Issues - Revision history

Kdtop at 16:39, 21 July 2015

2015-07-21T16:39:50Z

← Older revision		Revision as of 16:39, 21 July 2015
Line 12:		Line 12:
	<H2>Deferred RPCs</H2>		<H2>Deferred RPCs</H2>

	In order to increase efficiency, applications can run [[~~RPC_HELP_Deferred_RPCs~~\|RPCs in the background]].		In order to increase efficiency, applications can run [[RPC_HELP_Deferred_RPC_Overview\|RPCs in the background]].


	<H2>Remote RPCs</H2>		<H2>Remote RPCs</H2>

	In order to work with patient data across sites, applications can run [[~~RPC_HELP_Running_RPCs_on_a_Remote_Server~~\|RPCs on a remote server.]]		In order to work with patient data across sites, applications can run
			[[RPC_HELP_XWB_REMOTE_Options_for_Running_RPCs_on_a_Remote_Server\|RPCs on a remote server.]]

	<H2>Blocking RPCs</H2>		<H2>Blocking RPCs</H2>

	Applications can install RPCs that should be used only in certain contexts. It is possible to [[~~RPC_HELP_block_access_to_an_RPC~~\|block access to an RPC]].		Applications can install RPCs that should be used only in certain contexts. It is possible to [[RPC_HELP_M_Entry_In_RP_File_Blocking_RPC\|block access to an RPC]].


	<H2>Silent Login</H2>		<H2>Silent Login</H2>

	In special cases, applications can use one of two types of [[RPC_HELP_Silent_Login\|Silent Login]] to log in users without the RPC Broker prompting for login information.		In special cases, applications can use one of two types of [[RPC_HELP_Silent_Login\|Silent Login]] to log in users without the RPC Broker prompting for login information.

Kdtop at 20:37, 3 July 2015

2015-07-03T20:37:20Z

← Older revision		Revision as of 20:37, 3 July 2015
Line 27:		Line 27:
	<H2>Silent Login</H2>		<H2>Silent Login</H2>

	In special cases, applications can use one of two types of Silent Login to log in users without the RPC Broker prompting for login information.		In special cases, applications can use one of two types of [[RPC_HELP_Silent_Login\|Silent Login]] to log in users without the RPC Broker prompting for login information.

Kdtop: Created page with " RPC Broker Help Home

Application Issues

Application Version Numbers

There may be a need to set or pass application version numbers. Th..."

2015-07-03T20:34:48Z

Created page with " RPC Broker Help Home <H3>Application Issues</H3> <H2>Application Version Numbers</H2> There may be a need to set or pass application version numbers. Th..."

New page

[[RPC_Broker_Help| RPC Broker Help Home]]
<H3>Application Issues</H3>
<H2>Application Version Numbers</H2>

There may be a need to set or pass application version numbers. The suggested format is as follows:
<CODE>VersionNumber_PatchNumber(3 digits)</CODE>

Thus, Patch 22 of Version 8.2 would be:
<CODE>8.2022</CODE>

<H2>Deferred RPCs</H2>

In order to increase efficiency, applications can run [[RPC_HELP_Deferred_RPCs|RPCs in the background]].

<H2>Remote RPCs</H2>

In order to work with patient data across sites, applications can run [[RPC_HELP_Running_RPCs_on_a_Remote_Server|RPCs on a remote server.]]

<H2>Blocking RPCs</H2>

Applications can install RPCs that should be used only in certain contexts. It is possible to [[RPC_HELP_block_access_to_an_RPC|block access to an RPC]].

<H2>Silent Login</H2>

In special cases, applications can use one of two types of Silent Login to log in users without the RPC Broker prompting for login information.