Home JD Edwards EnterpriseOne CombiRoles

CombiRoles

For JD Edwards EnterpriseOne

Product Overview

Using multiple, process‐based roles is considered the best practice in JD Edwards. But in standard E1, it's complex to manage role security conflicts when they arise.

CombiRoles offers automated issue resolution and full security information directly in your JDE. Why not become a CombiRoles addict today and save yourself time?

Benefits

Maximize your investment with automated conflict resolution
Save time for key resources on security troubleshooting
Be pro-active, control, and test your security before go-live
Flexible and seamless management +20 UDO security types
Avoid business interruption and helpdesk questions on user access
Fully auditable reports
Optimized system performance with fewer security records
Achieve best practices within standard JD Edwards

Key Features

Features	Standard JDE	CombiRoles
Unlimited Roles	30 Roles Limit	Limitless
Access Conflict Resolution	Manual & Time Consuming	Automated Resolution
Comprehensive Access Visibility	Not Available	Security / Management Reporting
Company & BU Access	High Maintenance: 1 Complex Role Per User	Low Maintenance: Multiple Simple Roles
UDO Info	Manually Reconcile	Automated & Accumulated Net Effect
Simple Tailored Menu	Not Available	Automated & Consolidated
Flexible SoD Validation	Not Available	Optional Automation
Role Promotion Between Environments	Manual Dual Entry	Automated
Roles Within Roles	Not Available	Streamlined & Automated
Security Change Management	Not Available	Workflow Enabled

Get started with CombiRoles today!

Install ALLOut in JD Edwards

Once you have licensed the software, simply login to the customer portal, download and install the latest version.

Learn with the ALLOut Academy

Get on-demand training to help you achieve achieve your objectives in JD Edwards.

Implement Features with Services Partners

Consult one of our partners to assist with your projects or ongoing managed service requirements.

Visit ALLOut Academy

Contact an ALLOut Partner

Discover our industry leading expertise

Industry Insights

Access Management in JD Edwards (JDE) Security
July 1, 2021
Access management is the process of identifying, tracking, controlling and managing authorized or specified user's access to a system, application or any IT instance.

Blindfolded Exposure: Identifying Rogue Security Elements for Clean-Up
December 9, 2021
We'll be discussing risks and costs associated with rogue security elements in your JD Edwards system and what you can do to decrease those risks.
Watch On-Demand

Upcoming live events

No upcoming webinars found

Empower your security team

Save time, enhance risk visibility and be audit-ready with ALLOut Security for JD Edwards.

Request a Demo

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

CombiRoles

For JD Edwards EnterpriseOne

Product Overview

Benefits

Key Features

Related Products

ProfilePlus

StartOut

Risk Management