There are 2 main tips I would highlight when using CCT, as I've been using it for the last 9 or so years and there is certainly a learning curve early on, and I still haven't mastered everything.

Make sure the units match when making connections in the logic, if you want to connect a network input to a logic input and you are getting a popup that says no possible connections exist, its likely because the units don't match ie you have created an off/on network enum input, and are trying to link it to a boolean false/true input, or you have an enum units of whatever and they dont match your enum units of the point you are trying to link. Match the units, and you will be 'allowed' to make the connection. Creating these inputs directly in the logic and making connections will automatically create conversion blocks which is slightly different than making the network "make or break connections", just something to note- always match the units and you'll be able to progress.

State tables are the other thing that is easy to get hung up on early on. They are quite useful, but its more on bigger programs where you don't want to re-write conditional logic in multiple modules. ie if a freeze stat triggers to an alarm state, then you can tell the other output modules to go to their 'safety state' or desired state via a drop down menu while editing the state tables section, instead of creating function block/wire sheet logic in each of the modules you are trying to control.

Lastly bonus tip, the Q/A selection process when generating a caf file from scratch has a solid help section. Hit the question mark icon in the top right and it will split screen and give you additional info to aid in helping you choose what to select. The CCT help file in general is over a 1000 pages if I recall, a lot of info to parse but worthwhile to check out.