The setting method of DCGroup

[Former Member]

Hello,

We've just have a problem in DC functionality of ME 5.2. Please ask the solution.

There are two environment, test environment(Env1) and productional environment(Env2).

Behavior of DC500 differs as follows in these two environments.

The behavior which we wish is behavior in Env2.

How can we do that the same behavior between Env1 and Env2?

>Behavior of DC500

SFC Status：New or In Queue

-Env1：DC500　available

-Env2：DC500　unavailable

SFC Status：Active

-Env1：DC500　available

-Env2：DC500　available

>Our Setting

We made DC group and attached it to following attach points.

router and operation step.

Regards,

Yousuke Murakami

[Former Member]

Hello,

In DC group maintenance set "data to collect at" to Always for the dc group.

Regards,

German

[Former Member]

Thank you for answering my questin.

Similarly we have set up DC maintenance in two environments (Env1 and Env2).

Our setting are as follows.

Main Tab

Status:Releasable

Collection Type: SFC

Collect Data At: Anytime

Collection Method: Manual - Single

User Authentication Required : No checked

Current Version : Checked

Pass/Fail Group : No checked

ERP Group : No checked

Attached Tab

ATTACHMENT POINTS : Routing and Routing Step

However, operations differ in two environments.

When SFC Status：New or In Queue

-Env1：DC500　available

-Env2：DC500　unavailable

Is there any setup which controls operation of DC group in addition to DC maintenance?

Please let me know.

In addition, we use ME of the version 5.2 SP05 Patch 16.

Best Regards,

Yousuke Murakami

[sergiy_katerinich]

Yousuke-san,

I would say that the behavior of Env1 when DC500 is available for New/InQueue SFCs is the correct one as soon as Operation and Resource fields of POD are populated with correct values (I assume you use Standard Web POD, not a Rich POD).

There is a system rule "Allow Multiple Data Collection" which affects the way of how DC500 works, though I'm not sure it is relevant to your case.

As to why Env2 behave differently, maybe it is because of old DC Groups created in previous releases. Please try to create a new DC Group and then replicate the issue.

Regards,

Sergiy