版權聲明:本文為部落客汪子熙原創文章,未經部落客允許不得轉載。 https://jerry.blog.csdn.net/article/details/87348351
Text determination execution with two different mode
For opportunity creation case, the text determination procedure will be executed two times, each with different execution mode.
[First time]{.underline}
The trigger point is FM CRM_TEXT_DETERMINATION_EC,
![](https://img.laitimes.com/img/__Qf2AjLwojIjJCLyojI0JCLiAjM2EzLcd3LcJzLcJzdllmVldWYtl2Pn5GcucTNrlHeqh2Mzc3LcNDO0YjM0UzLcVmdhNXLwRHdo9CXt92YucWbpRWdvx2Yx5yazF2Lc9CX6MHc0RHaiojIsJye.png)
since this FM is registered as a callback via 1order event framework, detailed customizing could be found below:
Note: under this mode ( mode value C - dynamic read ),
only text objects configured as “Transfer = C” will be handled:
This logic could easily be found in code line 136: ( only text object with transfer = C can have chance to execute subroutine determine_text )
[Second time]{.underline}
this time the mode is hard coded as B:
B means save text:
Under this mode, only those text objects which DO NOT have transfer = C will be handled.