The hasRole() method is for checking if the currently logged in user has a specific role. It accepts one argument (the name of the role to check that the user has, and returns a boolean value indicating whether the user has the specified role or not).
- The Interface
- Lists and Forms
- UI Customization
- Understanding Data and Relationships
- Tasks and Workflows
- UI and Data Policies
- User Administration and Security
- Introduction to Scripting
- To script, or not to script?
- Client side versus server side APIs
- Where scripting is supported
- Access controls-executes on: server
- Business rules-executes on: server
- Client scripts and catalog client scripts-executes on: client
- Condition builder (and the URL)-executes on: server
- Default value-executes on: server
- Script Includes-executes on: server
- UI actions-executes on: client and/or server
- UI policies and catalog UI policies-executes on: client
- UI scripts-runs on: client
- Workflow activities-executes on: server
- Integrated development environment
- Summary
- The Server-side Glide API
- The structure of an API class
- Server-side APIs
- GlideRecord
- Initialize
- addQuery()
- addNullQuery() and addNotNullQuery()
- canRead(), canWrite(), canCreate(), and canDelete()
- deleteRecord() and deleteMultiple()
- get()
- getDisplayValue()
- getValue() and getUniqueValue()
- hasNext()
- initialize() and insert()
- next()
- orderBy() and orderByDesc()
- query()
- setAbortAction()
- setLimit()
- setValue()
- setWorkflow()
- update() and updateMultiple()
- GlideElement
- GlideDateTime
- GlideSession
- GlideSystem
- GlideUser
- Client-side APIs
- GlideAjax
- GlideForm (g_form)
- Summary
- The Client-side Glide API
- Server-side Scripting
- Client-side Scripting
- Debugging
- Pro Tips
hasRole()
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.