CM: Relationship between Note created in Fiori UI and webclient UI

Created by Jerry Wang, last modified on Jan 13, 2015

Fiori UI上给Opportunity创建一个Note:

 

CM: Relationship between Note created in Fiori UI and webclient UI

 

 

HTTP post的request payload里就只有opp guid和user输入的note内容: 

 

CM: Relationship between Note created in Fiori UI and webclient UI

 

 

后台返回的response也只有这两个attribute:

 

CM: Relationship between Note created in Fiori UI and webclient UI

 

 

最后到webclient UI上却发现两条只读的text,类型为Description和Preparation

 

CM: Relationship between Note created in Fiori UI and webclient UI

 

 

 

后台实现:

 

 

直接用OPEN SQL 找当前创建的opportunity的transaction type对应的text determination 信息。

 

 

Opportunity 对应的text object type hardcode成CRM_ORDERH,changeable的属性也写死成P,因此当前的实现,通过Fiori UI创建出来的note 类型都为log ( changeable = P )

CM: Relationship between Note created in Fiori UI and webclient UI

 

最后Opportunity OData的实现并没有call 底层的text API,而是直接call One order的modification,

CM: Relationship between Note created in Fiori UI and webclient UI

 

只需要把text determination ID和待创建的note content和language传入 modify FM:

CM: Relationship between Note created in Fiori UI and webclient UI

 

在webclient UI上看到两个不同text type的note的原因是因为backend system 配置里,指定类型为P的text的content会自动transfer到 changes = R的text里,即Description和Preparation。

CM: Relationship between Note created in Fiori UI and webclient UI

 

 

 

 

CM: Relationship between Note created in Fiori UI and webclient UI

上一篇:SAP Fiori element框架template的框架加载逻辑


下一篇:Fiori自学材料