BLUEPRINT 4D – Las Vegas!

Join the ALLOut Security team at the Venetian in Las Vegas, for what’s set to be yet another engaging conference!

Home » Events » BLUEPRINT 4D - Las Vegas!

BLUEPRINT 4D – Las Vegas! by ALLOut Security

Nothing showcases the JD Edwards community like The JD Edwards Forum at BLUEPRINT 4D! Join the ALLOut Security team at the Venetian in Las Vegas, for what’s set to be yet another engaging conference! Get expert advice on moving your JDE objectives forward from our AOS product team and Oracle company reps during 120+ sessions, keynotes & demos! Early Registration Ends 27th February 2025: https://questoraclecommunity.org/events/conferences/blueprint4d/register/

Date: Monday 9th June - Friday 13th June

Location: The Venetian, Las Vegas

Schedule

Monday

3:00 PM - 7:00 PM Early Reg Happy Hour

5:00 PM - 7:00 PM Tech SIG Board Meeting

7:00 PM - 10:00 PM RUG Social Party (Register here)

Tuesday

11:00 PM - 11:45 PM Tech SIG General Meeting

5:45 PM - 8:30 PM Booth Open - Showfloor Reception

7:30 PM -10:00 PM Flight Club Social Party (with Terillium + ReportsNow) (Register here)

Wednesday

7:00 AM - 9:00 AM Customer Appreciation Breakfast (with Circular Edge) (Register here)

11:00 AM - 3:00 PM Booth Open

11:15 AM - 12:00 PM Tech SIG Roundtable: Maintaining & Upgrading JDE

3:00 PM - 3:45 PM Granite's Compliance Upgrade: Streamlined and at a Fraction of the Cost

4:45 PM - 6:15 PM Booth Open

Thursday

9:00 AM - 2:00 PM Booth Open

12:10 PM - 12:40 PM Ask & They Will Answer - Quick-fire Q&A with JDE Security and Compliance

7:00 PM - 10:00 PM Quest Party

What else do we have in store for you? Stay tuned and subscribe to get the latest updates on AOS at BLUEPRINT 4D!+

Date: Monday 9th June – Friday 13th June

Location: The Venetian, Las Vegas

What else do we have in store for you? Stay tuned and subscribe to get the latest updates on AOS at BLUEPRINT 4D!

Schedule:

Discover our industry leading expertise

Industry Insights

Row Security in JD Edwards – A Balancing Act
July 1, 2021
Row Security can be a necessity for many JDE implementations but, very detailed row security can result in excessive effort put into maintaining security records as well as system performance issues.

Easy visibility to security access for program, data or UDO security in JDE
January 14, 2020
Let ALLOut help with quick and easily delivered views of existing user or security role access. We can give easy visibility of security access for program, data or UDO security.
Watch On-Demand

Upcoming live events

BLUEPRINT 4D – Las Vegas!
9 Jun 2025, 12:00 am
Join the ALLOut Security team at the Venetian in Las Vegas, for what’s set to be yet another engaging conference!
View Event
Implementing Access Change Control in JD Edwards
May 21, 2025
In this joint webinar hosted by ERP Suites and supported by ALLOut Security, you’ll learn how to implement a secure, repeatable process that protects production environments without slowing down your team.
Register Now

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.

BLUEPRINT 4D – Las Vegas!

Discover our industry leading expertise

Industry Insights

Row Security in JD Edwards – A Balancing Act

On-demand webinars

Easy visibility to security access for program, data or UDO security in JDE

Upcoming live events

BLUEPRINT 4D – Las Vegas!

Implementing Access Change Control in JD Edwards

Empower your security team