天天看点

is transfer = C ( only read dynamically) not supported in one order scenario

我们在做complex note相关的customizing时,Transfer field一直留空。如果维护成type C会是什么behavior?

is transfer = C ( only read dynamically) not supported in one order scenario

Through testing, the note type marked with “Transfer = C” is not supported in one order scenario. This is confirmed by the note colleague in incident 1580009248.

If you try to create note with such type in WebUI, creation will not be done, you get a warning message in WebUI:

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-UDL1fMn4-1605451644490)(https://user-images.githubusercontent.com/5669954/59321942-b35c4680-8d06-11e9-82f1-4186b4bf507f.png)]

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-WeTMXcAO-1605451644492)(https://user-images.githubusercontent.com/5669954/59321943-b3f4dd00-8d06-11e9-854c-46ae4b5bea87.png)]

If we do the same thing in Fiori, the error message does not have chance to pass out:

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-cHjHczMZ-1605451644493)(https://user-images.githubusercontent.com/5669954/59321946-b48d7380-8d06-11e9-835e-dc842618bbfe.png)]

Thus end user will never see this error message, instead he could only see a “Note Saved” information in UI, actually it is not, and he could NOT see any note under the selected note type. This behavior is confusing.

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-mByGHD0m-1605451644494)(https://user-images.githubusercontent.com/5669954/59321947-b48d7380-8d06-11e9-9919-0901639baf9e.png)]

继续阅读