Essentially the common attribute of Hammocks is that their duration is driven by other activities but every software might have a particular implementation on how they work, some software allows for multiple predecessors either ss or ff with the links having their own calendar independent of the predecessors and successors activities.
I do not make much use of hammock activities as when resource loaded the resources are not leveled. Still hammock activities when needed are very useful. The following example reflects the impact of a delay to an activity whose duration varies in function of the delay. A perfect fit for displaying the effect of duration and costs on prolongation claims. The sample is from an actual claim where the job was delayed by the re-design and relocation of one building at the Owner's request.
Landscape maintenance is part of the original contract to start as soon as needed, 10 calendar days after start of landscaping and finish 30 calendar days after finish of job at project delivery. Note resource calendars can be different but must be compatible with activity calendar, using perhaps different workdays while ss lag calendar is in calendar days as required by watering needs and ff lag calendar is in calendar days as defined by the contract. In this job activities were scheduled using regular workweek as per contract, work on week end is not allowed unless asked on time and some reimbursements are done to pay extra inspection costs. The claim is for the difference between 19,200 and 133,200 in this item alone.
Note that resource B might work on other days but landscape maintenance is to be done only on Thursdays and/or Fridays. Here the activity calendar will determine when can B work on the activity.
What is important is that you realize that when transferring data from one software to another or when analyzing other software the behavior of the hammock might differ. Not all software are created equal, keep this always in mind.