advanced developer day 2

Advanced Developer Boot Camp 1

o

o

o

o


Architecture

Integration

DevelopmentUser Experience

Life-cycle

Developer Adv. Developer


Orchestration

Modules

End-user

Modules

Library

Modules

Core

Modules

No Upward

references


Orchestration

Modules

End-user

Modules

Library

Modules

Core

Modules

No Upward

references

No side references

among orchestration or

end-user modules


Orchestration

Modules

End-user

Modules

Library

Modules

Core

Modules

No Upward

references

No side references


end-user modules


Orchestration

Modules

End-user

Modules

Library

Modules

Core

Modules

No Upward

references

No side references


end-user modules

No role

based logic

• No end-user screens

• Read-only entities

No Business

logic or core

entities


•

•

•


•

•

•

•


1. Disclose

Iteration


Awesome hands-on! @outsystems

#advdevbootcamp


Move elements to library module

MSIN_Layout


Extract new core or

move to

CAN_Utilitários_Proc


Search in all applications for

violations to CAN_MCFBackoffice


2. Clone

3. Rename 4. Rename

5. Remove screens

and keep core

elements

6. Remove core and

keep screen

elements

7. Reference

1. Identify consumed

elements

Original Module

is now a core

↓

consumers not affected

Cloned Module keeps

the original name

↓

URLs not affected


http://www.outsystems.com/forge/component/496/refactor/


•

•


No upward

references

No side references


end-user modules


End-user

#1

Core

A

Library

A

Core

B

Library

B

End-user

#2

Core

C

Library

C

Core

D

Library

D

End-user

#1

Core

A

Core

B

Library

A

Library

B

1st project

End-user

#2

Core

C

Library

C

Core

D

Library

D

2nd project

3rd project


End-user

#1

Core

A

Core

B

Library

A

Library

B

End-user

#2

Core

C

Library

C

Core

D

Library

D

End-user

#1

Core

A

Library A

Core

B

Library

B

Core

C

Library

C

End-user

#2

Core

D

Library D


No Upward

references

No side references


end-user applications


Stable

module 2

New

module

Stable

module 1

…

Young module with high change

frequency

Unecessary impacts


New

molule

Stable

module 2

Stable

module 1

Split

… No longer affected


Module 3Module 1 Module 2

Owner 2Owner 1

Who is responsible?


Owner 1

Molule 1

Owner 2

Module 3Module 2

Promote ownership

Split


Simulation

Portal

Engines Policies

…Auto

…Life

…Property

Different project dates

Auto

Business

Life

Business

Property

Business


Each Line-of-Business can be deployed

independently

Auto

Business

Life

Business

Property

Business

…Auto

…Life

…Property

Engines Policies

Simulation

Portal


Too many violations to benefit

from LifeTime deployment

process!


Extract core and

library modules to a

new core application


Move to core

Application


Remove shared

core modules from

End-user

applications


o

o

o


o

o


o

o

o

o

o

o

• GenericExtendedActions.Audit(AppInfo.GetAppInfo().OsContext, <Message>, <ModuleName>);

o

• GenericExtendedActions.audit(AppInfo.getAppInfo().getOsContext(), <Message>, <ModuleName>);


o

o

o

advanced developer day 2

Software