AGRESSO 5'5 Technical

1
AGRESSO 5.5 Technical

• Herbert Van Zyl, Agresso RD
• Ryan Gloeckler, Agresso Travel

2
Evolution
vs
Revolution
3
Goals of AGRESSO 5.5

• Future proof
• Flexible
• Modern
• Integration
• Long lifespan
• Secure Investment

4
Focus on Architecture not Technology

• Technology changes
• Architecture stays the same

5
AGRESSO 5.5 interesting facts

• Technical and architecture started early 2001
• 270,000 development hours
• Fixed 13,000 tickets
• Reviewed 2 million lines of codes
• 30 development teams in 3 phases
• 2000 pages of release notes
• 3,312 hours of subsidiary testing

6
Architecture evolution
7
Evolution
REMEMBER
vs
Revolution
8
5.5 Changes Expand fields

• Transaction numbers 8 ? 12
• Attribute values 8-8-8-8-12-4-4 ? 12
• Reporting attributes 25
• Account 8 ? 12
• Attribute Id 2 ? 4
• Customer/Supplier ID numeric ? alpha 12
• Descriptions/texts various ? 255
• Unicode enabled

9
5.5 Changes Misc

• Minidumps
• Easier to find intermittent errors
• DB temporary tables
• Better performance
• Web help
• Accessible from SmartClient and Self Service

10
5.5 Changes Management Console

• AGRESSO Administrators have advanced access

11
5.5 Changes Management Console

• One service, multiple queues

12
5.5 Changes Management Console

• Simplified connections and configuration

13
5.5 Changes Management Console

• AGRESSO Utilities available

14
5.5 Changes Customization Framework

• Links, Flexifields and Page setup/Window options
• VBA still exists, lessons learned applied to
• AGRESSO Customization Tools ACT
• .NET-based
• Client, Server, TopGen, FrameWork and Common
• Not immediately available for public use

15
(No Transcript)
16
Integration example
data
External application
Authenticator
Inbound pipeline
Outbound pipeline
component
Reply
Snapshot

• Snapshot
• Receipt date/time
• Unique identifier
• Data before/after processing

data
data
component
component
XSLT transform
data
Snapshot
Business process
data
data
AGRESSO application
17
5.5 Changes Workflow
18
5.5 Changes Access/Data control

• Role based configuration
• Control access to product features and functions
• Control access to data
• One person, multiple roles

19
5.5 Changes Document Archive

• Attach, link or store documents
• View, edit or delete documents
• Search for documents based on indexes
• Check documents in/out
• Create documents from templates
• Load documents from a scanner or folder
• Store output from reports
• Documents accessible from Web

20
User interface

• User interface generator (TopGen)
• Reuse screen definition across multiple
  platforms
• Easily create UI to fit specific needs
• Self Service (Web)
• Time expense, approvals, workflow tasks,
  information analysis, HR self service, etc
• Smart Client (Windows)
• Budgeting, heavy transaction entry, workflow
  design, report creation, etc.

21
User interface

• Lets have a look