On Mon, Oct 12, 2015 at 11:22 AM, Sandro Bonazzola wrote:
>
>
> On Mon, Oct 12, 2015 at 10:06 AM, Simone Tiraboschi
> wrote:
>>
>>
>>
>> On Mon, Oct 12, 2015 at 7:29 AM, Yedidyah Bar David
>> wrote:
>>>
>>> On Sun, Oct 11, 2015 at 10:36 PM, Fabian Deutsch
>>> wrote:
>>> > Hey,
>>> >
>>> > latel
On Mon, Oct 12, 2015 at 10:06 AM, Simone Tiraboschi
wrote:
>
>
> On Mon, Oct 12, 2015 at 7:29 AM, Yedidyah Bar David
> wrote:
>
>> On Sun, Oct 11, 2015 at 10:36 PM, Fabian Deutsch
>> wrote:
>> > Hey,
>> >
>> > lately we had the issue that the answer file for the engine in the HE
>> > flow chang
On Mon, Oct 12, 2015 at 7:29 AM, Yedidyah Bar David wrote:
> On Sun, Oct 11, 2015 at 10:36 PM, Fabian Deutsch
> wrote:
> > Hey,
> >
> > lately we had the issue that the answer file for the engine in the HE
> > flow changed (it required an additional answer).
>
> "in the HE flow" specifically?
>
On Sun, Oct 11, 2015 at 10:36 PM, Fabian Deutsch wrote:
> Hey,
>
> lately we had the issue that the answer file for the engine in the HE
> flow changed (it required an additional answer).
"in the HE flow" specifically?
As discussed in private, this might best (?) be solved by adding an option
to
Hey,
lately we had the issue that the answer file for the engine in the HE
flow changed (it required an additional answer).
Currently the answerfile is maintained by node in the engine appliance.
I wonder if it wouldn't make more sense to keep the answer file (which
is solely used for the HE flo
