Yet another BizTalk Naming Guideline Recommendations

For all BizTalk orchestration shapes, I would recommend to call a shape with its name (or its shorthand) and suffix it with a succint description. This is only a recommendation. You don't have to follow this convention. The recommendation strives to promote a common set of guidelines.

...................................................................

              Shape  Short       Example

...................................................................

 Call Orchestration  CallOdx     CallOdx_AssembleReply

         Call Rules  CallRule    CallRule_LoanDecisioning

         Compensate  Compensate  Compensate_BadTransactions

  Construct Message  Mkmsg       Mkmsg_GetEntityParams

             Decide  Decide      Decide_ProcessBorrower

              Delay  Delay       Delay_OneHour

              Group  Grp         Grp_GetFirstEntity

             Listen  Listen      Listen_IncomingReq

               Loop  Loop        Loop_ProcessAllApplications

 Message Assignment  Assign      Assign_EntityMatchResultToReplyMsg

   Parallel Actions  Para        Para_GetMatchAndMkReply

              Port*  Port        Port_GetEntities

            Receive  Recv        Recv_AppReq

               Send  Send        Send_AppRep

Start Orchestration  Init        Init_PlaceOrder

            Suspend  Susp        Susp_CreditEvaluationOdx

          Terminate  Stop        Stop_CreditEvaluationOdx

    Throw Exception  Throw       Throw_UnknownReqException

          Transform  Xform       Xform_GetEntityParams

* Since orchestration's port name has nothing to do with the transfer protocol, the name should not contain the word like Soap, Http, File, etc.