RPC HELP App Issues: Difference between revisions

From VistApedia
Jump to navigationJump to search
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..."
 
No edit summary
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.

Revision as of 20:37, 3 July 2015

RPC Broker Help Home

Application Issues

Application Version Numbers

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

Thus, Patch 22 of Version 8.2 would be: 8.2022


Deferred RPCs

In order to increase efficiency, applications can run RPCs in the background.


Remote RPCs

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


Blocking RPCs

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


Silent Login

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.