Text determination execution with two different mode

Created by Jerry Wang on Feb 16, 2015

For opportunity creation case, the text determination procedure will be executed two times, each with different execution mode.

First time

The trigger point is FM CRM_TEXT_DETERMINATION_EC,

Text determination execution with two different mode

 

since this FM is registered as a callback via 1order event framework, detailed customizing could be found below:

Text determination execution with two different mode

 


Note: under this mode ( mode value C - dynamic read ), 

Text determination execution with two different mode

 

only text objects configured as "Transfer = C" will be handled:

Text determination execution with two different mode

 

This logic could easily be found in code line 136: ( only text object with transfer = C can have chance to execute subroutine determine_text )

Text determination execution with two different mode

 

 

Second time

  

this time the mode is hard coded as B: 

Text determination execution with two different mode

 

B means save text:

Text determination execution with two different mode

 


Under this mode, only those text objects which DO NOT have transfer = C will be handled.

Text determination execution with two different mode

上一篇:使用js实现ajax的get请求步骤


下一篇:[FAQ] docker-compose MySQL8 ERROR: Different lower_case_table_names settings for server