VA API Changes (V9.0)

VA: Verify Access 


Elliott V9.0 supports a series of 999 security flags to control access by users to specific features in the software.  At runtime, the VA,nnn API is sent (where nnn is a number identifying the security flag) and either “Y” or “N” is returned in SCREEN-ANSWER, indicating whether or not the user has authority to perform the function.  In addition, the security literal is returned in SCREEN-LITERAL.

The VA API will search for a flag setting in the following order:

The company-specific record for the user in the SYRIGHTS file.
The company-00 record for the user in the SYRIGHTS file.
The company-wide default setting in SYRIGHTS.

If the record is not found, then the API will continue to the next scenario.  The company-specific and company-00 settings for a user can be set using the Security Setup menu under Password Setup from the Utilities menu on the main menu.

The company-wide default settings can be set using the Global Security Setup menu under System after selecting Global Setup under Utilities on the main menu.

The changes displayed in bold below are changes to the API for V9.0. 

Screen Parameters: VA,00 

Clears the NS Control File Cache, called whenever the Company changes. 

This function is no longer necessary in v9.0. 

Screen Parameters: VA,PG,by,01,02,PK

Verifies whether or not SMA-USER-NAME has access to the specified menu option, (e.g., VA,PG,M ,03,00,AR Screen-Alpha-Field=ARCUSMNT for delete mode of Customer File Maintenance)

by = passed byte for program (M for maintenance, P for Posting, I for Inquiry, etc.)

01 = menu level

02 = submenu-level

PK = Package indicated in the SYSEGUID table

Screen-Alpha-Field = program name to check

Returns Y or N in SCREEN-ANSWER  and the menu literal in SCREEN-LITERAL.

CLS

Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. PSQL Database Names And DDF Convention
  16. ElisyscdService
  17. EliNoteService
  18. El2rstimService
  19. EliOrderService
  20. ItemInquiry
  21. EliitmiqService
  22. EliShiptoService
  23. El2getfrService
  24. Steps Required to Test ReportWriter in V8.2
  25. Installation of ElliottService, NETcellent’s Web Services for Elliott
  26. ResellerFinder
  27. EliaptrxService
  28. VendorInquiry
  29. EliloginService
  30. ElislsmnService
  31. EliserhsService
  32. EliatpobService
  33. ElievprcService
  34. ElihdtrxService
  35. ElicuswlService
  36. QueryTurnaround
  37. InvoiceInquiry
  38. ElicustmService
  39. EligetcdService
  40. OrderInquiry
  41. EliordiqService
  42. EliecontService
  43. EliautdpService
  44. El2CrCrdService
  45. Log-Timer / ElliottTimer.Ini Support
  46. Alpha Document Number Support (V8.5/V9.0)
  47. ElliottService System.TypeInitializationException
  48. Feature - Printing API to Dynamically Set Number of Copies
  49. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  50. DD API Changes (V9.0)
  51. Developing a New Elliott V8.3 ReportWriter User Defined Report (UDR)
  52. PA API (V9.0)
  53. ReportWriter Thresholds
  54. ReportWriter Delivery Strategy
  55. Animating COBOL Code in Elliott V8.5
  56. Validate License API
  57. AP API
  58. TP API: Temporary Path
  59. The lessons we learned from upgrading web service 8.2 to 8.5 in eStore

Feedback and Knowledge Base