Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324626 - [Rules] - Disconnect TransferType from InformationUnit-Type
Summary: [Rules] - Disconnect TransferType from InformationUnit-Type
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Remus (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tom Seidel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-07 04:29 EDT by Tom Seidel CLA
Modified: 2020-05-07 09:59 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Seidel CLA 2010-09-07 04:29:45 EDT 
Currently the Rule-Engine is very tightly coupled to the creation of new Information Units. Each Information Type can contribute a valid transfer type and a CreationTrigger to trigger a specific drop-rule. This is not very flexible. We need a information-unit creation call directly from a groovy script. This call sets the type of the newly created information unit. The script should have a parameter to configure if a dialog is shown. This would eliminate the extension validTransfer and creationTrigger.
Comment 1 Tom Seidel CLA 2012-12-13 10:25:53 EST 
fixed