People Functions

Thanks Mike - I'll update our internal guidance notes to reflect this position. We're currently on an exercise to refactor code to remove our reliance on fully deprecated plug ins however we do not have to worry too much about elements of a plug in being deprecated.  Cheers Paul. 

There isn't an easy way to do this since the deprecated APIs could be used in shared portions of the code and programmatic identification would be difficult.

I would not worry about the API removal unless the plugin itself is deprecated and replaced with something else (another plugin or OOTB functionality) - there is another HC finding for that, which identifies deprecated plugins.

H Mike - as the Healthcheck highlights deprecated API usage as follows : "Plug-ins using deprecated APIs require refactoring to use alternative APIs as they will be removed and stop working in a future release" - is the recommendation for customers to avoid using those particular functions that use said Deprecated API's ?

If so is there an easy way to flag up those functions ?

( I can do it manually by trawling the code in the plug in to see which function / smart service is affected - but would be really handy if the Healthcheck was able to flag it) 

Unfortunately, no. There is no way to remove the deprecated method.

Hi, I am trying to replace the deprecated API to the latest one in the Plugin code. In SetUserPreferences function, it uses ServiceLocator to get the UserProfileService. I'm not able to avoid the ServiceLocator since it uses User's service context to fetch the User's UserProfileService instance.
The UserProfileService from the injunction is specific to the default user(who runs the smart service). Is there is any other way to get the User's UserProfileService using the latest library?

//get user's service context
ServiceContext sc = ServiceContextFactory.getServiceContext(ups.getUser(user).getUsername());
UserProfileService userUps = ServiceLocator.getUserProfileService(sc);			

// get user preference and set locale
UserPreferences up = buildUserPreferences();

//set user preferences
userUps.setUserPreferences(up);

What are the valid values to pass into the timezone field on Set User Preferences?

The functions are not missing, they are deprecated and replaced by OOTB functions introduced in 18.4. The existing places where the functions are referenced should continue to work but you should use OOTB functions for all new development.

Regarding the error, I am not sure how to tie this back to the plugin. Do you have a stack trace from the logs that would help pinning this issue down?

The System Has Encountered an Error HTTP Code: 500 APNX-1-4198-019 An Error Has Occurred Expression evaluation error [evaluation ID = CZHWMV0I] at function a!adminRouter: An error occurred while executing a save: java.util.UnknownFormatConversionException: Conversion = 'D'

We have upgraded our Appian cloud to version 19. Now the plugin seems to be not working. Some functions are no longer available (missing basically). When we tried redeploying the plugin, we get the following error message:

Hello i forgot  un-deploy the Group Plugins function and the User And Group Management Application plugin.but the people plugin failed to deploy.i am seeing the weird scenerio some of the groupmanagement functios are not working now.What was the resolution for this type of situation

Thank you!

Regards,

Rajesh